[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MEXT] EXTENDED [WGLC] RFC 3775 bis / draft-ietf-mext-rfc3775bis
Hi all,
I reviewed the draft and I think it is ready to be sent to the IESG.
I have one minor comment on section 11.5.2.
The text does not cover the case of MN bootstrapping in home link. Here is a proposal:
OLD TEXT
11.5.2. Home Link Detection
When an MN detects that it has arrived on a new link using the
movement detection algorithm in use (Section Section 11.5.1,) it
performs the following steps to determine if it is on the home link.
o The MN performs the procedure described in Section 11.5.2x and
configures an address. It also keeps track of all the on-link
prefix(es) received in the RA along with their prefix lengths.
o If the home prefix has not been statically configured the MN uses
some form of bootstrapping procedure (e.g. RFC5026 [25]) to
determine the home prefix.
o Given the availability of the home prefix, the MN checks whether
or not the home prefix matches one of the prefixes received in the
RA. If it does, the MN concludes that it has returned home.
NEW TEXT
11.5.2. Home Link Detection
When an MN detects that it has arrived on a new link using the
movement detection algorithm in use (Section 11.5.1) or after bootstrapping, it
performs the following steps to determine if it is on the home link.
o The MN performs the procedure described in Section 11.5.3 and
configures an address. It also keeps track of all the on-link
prefix(es) received in the RA along with their prefix lengths.
o If the home prefix has not been statically configured the MN uses
some form of bootstrapping procedure (e.g. RFC5026 [25]) to
determine the home prefix.
o Given the availability of the home prefix, the MN checks whether
or not the home prefix matches one of the prefixes received in the
RA. If it does, the MN concludes that it is connected to the home link.
Thanks
Patrick
> -----Original Message-----
> From: mext-bounces at ietf.org [mailto:mext-bounces at ietf.org] On Behalf Of
> Laganier, Julien
> Sent: Friday, August 21, 2009 8:30 PM
> To: Laganier, Julien; mext at ietf.org
> Subject: [MEXT] EXTENDED [WGLC] RFC 3775 bis / draft-ietf-mext-
> rfc3775bis
>
> Greetings,
>
> There was only one review of the draft RFC3775bis so far and we need
> more to send this document to IESG thus we decided to extend the WGLC.
>
> Please review the specification and post a message to the mailing list
> if you think the document is ready to be forwarded to IESG before 2009-
> 09-11 6:00PM EST.
>
> --julien & marcelo, MEXT chairs
>
> > -----Original Message-----
> > From: mext-bounces at ietf.org [mailto:mext-bounces at ietf.org] On Behalf
> Of
> > Laganier, Julien
> > Sent: Wednesday, August 05, 2009 8:20 AM
> > To: mext at ietf.org
> > Subject: [MEXT] [WGLC] RFC 3775 bis / draft-ietf-mext-rfc3775bis
> >
> > Folks,
> >
> > As discussed during the MEXT session in IETF-75 we're issuing a two
> > weeks WGLC on RFC 3775 bis <http://tools.ietf.org/html/draft-ietf-
> mext-
> > rfc3775bis-04> that will follow the two rules below:
> >
> > - this WGLC is NOT intended for re-opening discussions on issues that
> > were resolved during the revision process neither for bringing up new
> > issues.
> >
> > - this WGLC is intended to be sanity check to see whether the various
> > changes we agreed to made fit together. Editorial corrections are
> also
> > welcome.
> >
> > Please review the specification and post a message to the mailing
> list
> > if you think the document is ready to be forwarded to IESG before
> 2009-
> > 08-15 6:00PM PST.
> >
> > Thank you for your support.
> >
> > --julien & Marcelo, MEXT chairs
> >
> > _______________________________________________
> > MEXT mailing list
> > MEXT at ietf.org
> > https://www.ietf.org/mailman/listinfo/mext
> _______________________________________________
> MEXT mailing list
> MEXT at ietf.org
> https://www.ietf.org/mailman/listinfo/mext