Re: [16NG] Fw: I-D ACTION:draft-madanapalli-16ng-ipv4-over-802-dot-16-ipcs-00.txt
"Syam Madanapalli" <smadanapalli@gmail.com> Sat, 10 February 2007 05:51 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1HFl8j-00045S-8M; Sat, 10 Feb 2007 00:51:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1HFl8h-00045H-7U
for 16ng@ietf.org; Sat, 10 Feb 2007 00:51:11 -0500
Received: from nf-out-0910.google.com ([64.233.182.190])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFl8f-0007jY-SA
for 16ng@ietf.org; Sat, 10 Feb 2007 00:51:11 -0500
Received: by nf-out-0910.google.com with SMTP id l36so1457297nfa
for <16ng@ietf.org>; Fri, 09 Feb 2007 21:51:09 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
b=PfNKC63M1A9mXlPfpPMTXQiqWvEl/T2+sw/nGnktA/+0PxSPULqmEnbA9RIRCx2MWN6CUPDdk1+eW5ZJtaFgFu/VP0/gNUaFKHj+YhY9wDSr1neS2GmCjK2ASp9ylRsLWCoGSDeAE31izghx/DEweA9RomWO799JcSRzu78M/ZM=
Received: by 10.49.65.15 with SMTP id s15mr2124270nfk.1171086668975;
Fri, 09 Feb 2007 21:51:08 -0800 (PST)
Received: by 10.49.92.12 with HTTP; Fri, 9 Feb 2007 21:51:08 -0800 (PST)
Message-ID: <10e14db20702092151s2fa09fbevb5075206a52b1904@mail.gmail.com>
Date: Sat, 10 Feb 2007 11:21:08 +0530
From: "Syam Madanapalli" <smadanapalli@gmail.com>
To: "Bruno Miguel Sousa" <bmsousa@dei.uc.pt>
Subject: Re: [16NG] Fw: I-D
ACTION:draft-madanapalli-16ng-ipv4-over-802-dot-16-ipcs-00.txt
In-Reply-To: <45CC5CBB.4040103@dei.uc.pt>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <004f01c74bdf$92a69790$8046fea9@your655e9d6f61>
<45CC5CBB.4040103@dei.uc.pt>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
<mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>,
<mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org
Thanks Burno for the comments. On 2/9/07, Bruno Miguel Sousa <bmsousa@dei.uc.pt> wrote: > Dears > > > Here is my contribution to this draft. > > General comments: > > I think the text is well written and easy to understand. > The overall operations of IPv4 (address assignment, multicast, ...) > are presented in the document. > > > Specific comments: > > 1) > The sentences in the abstract: > " > access. IEEE has specified several service specific convergence > sublayers (CS) for 802.16 which are used by upper layer protocols. > The ATM CS and Packet CS are the two main service-specific > convergence sublayers and these are a part of the 802.16 MAC which > the upper layers interface to. > " > I suggest to rewrite since 802.16 defines two service specific > convergence sublayers. > The term several does not seem correct imho. The sentences present some > repetition > when referring to upper layers. My suggestion: > > IEEE has specified the service specific convergence sublayers (CS) > in the 802.16 MAC to be used by upper layer protocols. > The ATM CS and the Packet CS represent the two main > service specific convergence sublayers for 802.16. Yes, I will make this change in the next revision. > > 2) > Some minor corrections. > " > Unit (MTU) and address assignment procedures for transmitting _IPv4_ > packets over IP Convergence Sublayer (IPCS) of IEEE 802.16. This > " > > " > be sent to MSs before they acquire IP addresses. The figure below > illustrates the network _architecture_. > " > > IPv4 and not IPv6 > " > _IPv4_ packets are transmitted in Generic 802.16 MAC frames as shown in > the following figure. > " > > remove: is > " > must be established. This connection _is_ consists of 802.16 MAC > transport connection between MS and BS and an L2 tunnel between BS > and AR. > " > > remove being > " > connection to the AR. BS reconstructs the payload header if the PHS > is in use before _being_ the packet is tunneled to the AR. > " > OK. Thanks. > > 3) > Section Maximum Transmission Unit > The value of 2038 is justified in the text. > In my opinion it is important to add references to justify the values > 1920 and 576. > > For instance for the 576 value I would add a reference to the RFC 1122 > to present the effective MTU to receive. OK. I will add this reference. Regards, Syam > > > > Kindly, > Bruno Sousa > > > Daniel Park wrote: > > IPv4CS document is now available at: > > http://www.ietf.org/internet-drafts/draft-madanapalli-16ng-ipv4-over-802-dot-16-ipcs-00.txt > > > > Daniel (Soohong Daniel Park) > > Mobile Convergence Laboratory, SAMSUNG Electronics. > > > > _______________________________________________ > > 16NG mailing list > > 16NG@ietf.org > > https://www1.ietf.org/mailman/listinfo/16ng > > > > > > > _______________________________________________ > 16NG mailing list > 16NG@ietf.org > https://www1.ietf.org/mailman/listinfo/16ng > _______________________________________________ 16NG mailing list 16NG@ietf.org https://www1.ietf.org/mailman/listinfo/16ng
- [16NG] Fw: I-D ACTION:draft-madanapalli-16ng-ipv4… Daniel Park
- Re: [16NG] Fw: I-D ACTION:draft-madanapalli-16ng-… Bruno Miguel Sousa
- RE: [16NG] Fw: I-DACTION:draft-madanapalli-16ng-i… Narvaez, Paolo (Paolo)
- Re: [16NG] Fw: I-D ACTION:draft-madanapalli-16ng-… Syam Madanapalli
- Re: [16NG] Fw: I-DACTION:draft-madanapalli-16ng-i… Syam Madanapalli