[prev in list] [next in list] [prev in thread] [next in thread]
List: ietf
Subject: Re: Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) P
From: Abdussalam Baryun <abdussalambaryun () gmail ! com>
Date: 2013-08-27 11:05:21
Message-ID: CADnDZ8_jfLdPk482KYy0=BYsqS1=XsFSi2OP3MXaGYoNvkwxBw () mail ! gmail ! com
[Download RAW message or body]
Reviewer: Abdussalam Baryun
Date: 26.08.2013
As per the IESG request for review dated 19.08.2013
++++++++++++++++++++++++++++++++++++
I support the draft, thanks, below are my comments,
Overall> The draft is about 3GPP Mobile Devices but the draft has no
normative reference to such device. The title of the draft SHOULD mention
that it is general profile or a proposal, where the abstract says
*specifies an IPv6 profile* which means not general, so the title SHOULD
say *An IPv6 profile*. Also the draft does not consider Mobile IP issues
nor RFC5213 into requirements. From the doc the reviewer is not sure does
the draft consider MANET issues or not needed for such devices or such
connections?
Abstract> This document specifies an IPv6 profile for 3GPP mobile devices.
AB> suggest> this document defines an IPv6 profile....
The document is missing an applicability statement section, which may be
found in one paragraph in section 1.1, but the reviewer would like more
details because the document is some how saying it is general requirements.
AB
On Mon, Aug 19, 2013 at 11:52 PM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the IPv6 Operations WG (v6ops) to
> consider the following document:
> - 'Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices'
> <draft-ietf-v6ops-mobile-device-profile-04.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-09-02. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
> This document specifies an IPv6 profile for 3GPP mobile devices. It
> lists the set of features a 3GPP mobile device is to be compliant
> with to connect to an IPv6-only or dual-stack wireless network
> (including 3GPP cellular network and IEEE 802.11 network).
>
> This document defines a different profile than the one for general
> connection to IPv6 cellular networks defined in
> [I-D.ietf-v6ops-rfc3316bis]. In particular, this document identifies
> also features to deliver IPv4 connectivity service over an IPv6-only
> transport.
>
> Both hosts and devices with capability to share their WAN (Wide Area
> Network) connectivity are in scope.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-profile/
>
> IESG discussion can be tracked via
>
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-profile/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
[Attachment #3 (text/html)]
<div dir="ltr"><div style>Reviewer: Abdussalam Baryun</div><div style>Date: \
26.08.2013</div><div style><br></div><div style>As per the IESG request for review \
dated 19.08.2013</div><div style>++++++++++++++++++++++++++++++++++++</div> <div \
style><br></div><div style>I support the draft, thanks, below are my \
comments,</div><div style><br></div><div style>Overall> The draft is about 3GPP \
Mobile Devices but the draft has no normative reference to such device. The title of \
the draft SHOULD mention that it is general profile or a proposal, where the abstract \
says *specifies an IPv6 profile* which means not general, so the title SHOULD say *An \
IPv6 profile*. Also the draft does not consider Mobile IP issues nor RFC5213 into \
requirements. From the doc the reviewer is not sure does the draft consider MANET \
issues or not needed for such devices or such connections?</div> <div><pre \
style="font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre \
style="font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre \
style="font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"> Abstract> \
This document specifies an IPv6 profile for 3GPP mobile devices.</pre><pre \
style="font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre \
style="font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"> \
<br></pre></div><div style>AB> suggest> this document defines an IPv6 \
profile....</div><div style><br></div><div style>The document is missing an \
applicability statement section, which may be found in one paragraph in section 1.1, \
but the reviewer would like more details because the document is some how saying it \
is general requirements.</div> <div style><br></div><div style>AB</div></div><div \
class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Aug 19, 2013 at 11:52 \
PM, The IESG <span dir="ltr"><<a href="mailto:iesg-secretary@ietf.org" \
target="_blank">iesg-secretary@ietf.org</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><br> The IESG has received a request from the IPv6 Operations \
WG (v6ops) to<br> consider the following document:<br>
- 'Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices'<br>
<draft-ietf-v6ops-mobile-device-profile-04.txt> as Informational RFC<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2013-09-02. \
Exceptionally, comments may be<br> sent to <a \
href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain \
the<br> beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
This document specifies an IPv6 profile for 3GPP mobile devices. It<br>
lists the set of features a 3GPP mobile device is to be compliant<br>
with to connect to an IPv6-only or dual-stack wireless network<br>
(including 3GPP cellular network and IEEE 802.11 network).<br>
<br>
This document defines a different profile than the one for general<br>
connection to IPv6 cellular networks defined in<br>
[I-D.ietf-v6ops-rfc3316bis]. In particular, this document identifies<br>
also features to deliver IPv4 connectivity service over an IPv6-only<br>
transport.<br>
<br>
Both hosts and devices with capability to share their WAN (Wide Area<br>
Network) connectivity are in scope.<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href="http://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-profile/" \
target="_blank">http://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-profile/</a><br>
<br>
IESG discussion can be tracked via<br>
<a href="http://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-profile/ballot/" \
target="_blank">http://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-profile/ballot/</a><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
</blockquote></div><br></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic