Subject: Re: [6lo] [6tisch] New Version Notification for draft-ietf-6lo-backbone-router-01.txt

From: AbdurRashidSangi <[email-masked]>
Date: Wed, 15 Jun 2016 08:55:48 +0000

Hello Pascal,

After reviewing "draft-ietf-6lo-backbone-router-01" following are some editorial suggestions, a question and a confusion:

1. Page 10, 4th para: "this by allowing" instead of "this be allowing".   
2. Page 11, 5th para: additional "can" in "this can can be".
3. Page 15, 6th para: "may fail if the multicast" instead of "may fail of the multicast".
4. Page 18, 4th para: "secondary for another one" instead of "secondary or another one".
5. Page 18, last bullet: "an address" instead of "an addresses".
6. Page 19, 3rd bullet: "status field" instead of "status filed".
7. Page 29, Req1.4: some text missing "6LRs, and this....".
8. AERO is mentioned 3 times, probably is EARO or otherwise "Authenticated Encryption with Replay prOtection" from "draft-mcgrew-aero-01":
       Page 12, 3rd para "AERO option"
       Page 21, 4th para "NA(AERO)"
       Page 22, 2nd para "NA(AERO)"
If it is the later case then more explanation seems required.
9. Question: 
	"As a proxy, the 6BBR uses an EARO option in the NS-DAD and the 
        multicast NA messages that it generates on behalf of a Registered
        Node, and it places an EARO in its unicast NA messages if and only if
        the NS/NA that stimulates it had an EARO in it."
Would it be NS that is multicast or the NA?
 
Hope you find above review useful.

Thanks.
Rashid Sangi,
Huawei, Beijing, China.

> -----Original Message-----
> From: 6tisch [mailto:[email-masked]] On Behalf Of Pascal
> Thubert (pthubert)
> Sent: 2016年3月19日 4:18
> To: [email-masked]
> Cc: [email-masked]
> Subject: Re: [6tisch] New Version Notification for draft-ietf-6lo-
> backbone-router-01.txt
> 
> Minor changes in the ARO option, there was a leftover field name and
> the lifetime was incorrectly indicated as 1 octet? It is 2 octets,
> expressed in minutes.
> 
> Cheers,
> 
> Pascal
> 
> 
> > -----Original Message-----
> > From: [email-masked] [mailto:[email-masked]]
> > Sent: vendredi 18 mars 2016 21:16
> > To: Pascal Thubert (pthubert) <[email-masked]>
> > Subject: New Version Notification for
> > draft-ietf-6lo-backbone-router-01.txt
> >
> >
> > A new version of I-D, draft-ietf-6lo-backbone-router-01.txt
> > has been successfully submitted by Pascal Thubert and posted to the
> > IETF repository.
> >
> > Name:		draft-ietf-6lo-backbone-router
> > Revision:	01
> > Title:		IPv6 Backbone Router
> > Document date:	2016-03-18
> > Group:		6lo
> > Pages:		33
> > URL:            https://www.ietf.org/internet-drafts/draft-ietf-6lo-
> backbone-
> > router-01.txt
> > Status:         https://datatracker.ietf.org/doc/draft-ietf-6lo-
> backbone-router/
> > Htmlized:       https://tools.ietf.org/html/draft-ietf-6lo-backbone-
> router-01
> > Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-6lo-
> backbone-router-
> > 01
> >
> > Abstract:
> >    This specification proposes an update to IPv6 Neighbor Discovery,
> to
> >    enhance the operation of IPv6 over wireless links that exhibit
> lossy
> >    multicast support, and enable a large degree of scalability by
> >    splitting the broadcast domains.  A higher speed backbone
> federates
> >    multiple wireless links to form a large MultiLink Subnet.
> Backbone
> >    Routers acting as Layer-3 Access Point route packets to registered
> >    nodes, where an classical Layer-2 Access Point would bridge.
> >    Conversely, wireless nodes register to the Backbone Router to
> setup
> >    routing services in a fashion that is essentially similar to a
> >    classical Layer-2 association.
> >
> >
> >
> >
> > Please note that it may take a couple of minutes from the time of
> > submission until the htmlized version and diff are available at
> tools.ietf.org.
> >
> > The IETF Secretariat
> 
> _______________________________________________
> 6tisch mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/6tisch