RE: Route Information Options in Redirect Messages

Hi Brian,

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> Sent: Tuesday, January 10, 2017 6:24 PM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>; 6man WG <ipv6@ietf.org>; INT Area <int-area@ietf.org>
> Subject: Re: Route Information Options in Redirect Messages
> 
> On 11/01/2017 06:55, Templin, Fred L wrote:
> > Hi Brian,
> >
> > I am looking at the section that says:
> >
> > "3.4.  Redirects
> >    There is potential for adverse interaction with any off-link Redirect
> >    (Redirect for a destination that is not on-link) message sent by a
> >    router in accordance with Section 8 of [RFC4861].  Hosts SHOULD apply
> >    off-link redirects only for the specific pair of source and
> >    destination addresses concerned, so the host's Destination Cache
> >    might need to contain appropriate source-specific entries.  This
> >    extends the validity check specified in Section 8.1 of [RFC4861]."
> >
> > What is being proposed in the document I submitted is the inclusion of
> > RIOs in Redirect messages for a *prefix* that is not on-link, as opposed
> > to a singleton destination. So, the same SHOULD in the paragraph above
> > would seem to apply also to prefix redirection the same as for ordinary
> > destination redirection.
> 
> I didn't want to bias your reading, but that was my conclusion too. If
> correct, maybe your draft needs to cite RFC8028 and augment it accordingly.

Yes, certainly it makes sense to cite RFC8028, and the next document version
will do that. Thanks very much for pointing this out.

Fred
fred.l.templin@boeing.com

> Regards
>     Brian
> 
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >> -----Original Message-----
> >> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> >> Sent: Monday, January 09, 2017 2:08 PM
> >> To: Templin, Fred L <Fred.L.Templin@boeing.com>; 6man WG <ipv6@ietf.org>
> >> Subject: Re: Route Information Options in Redirect Messages
> >>
> >> Fred,
> >>
> >> Can you check that there would be no adverse interaction with RFC8028,
> >> especially https://tools.ietf.org/html/rfc8028#section-3.4
> >>
> >> Regards
> >>    Brian
> >>
> >> On 10/01/2017 04:51, Templin, Fred L wrote:
> >>> See below for a new draft that proposes to update RFC4861 and RFC4191 to
> >>> permit the inclusion of Route Information Options in Redirect Messages.
> >>> This represents a backward-compatible extension to the IPv6 ND Redirect
> >>> function. Please review and comment on the list.
> >>>
> >>> Fred
> >>> fred.l.templin@boeing.com
> >>>
> >>> -----Original Message-----
> >>> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> >>> Sent: Friday, January 06, 2017 1:52 PM
> >>> To: i-d-announce@ietf.org
> >>> Subject: I-D Action: draft-templin-intarea-rio-redirect-00.txt
> >>>
> >>>
> >>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> >>>
> >>>
> >>>         Title           : Route Information Options in Redirect Messages
> >>>         Author          : Fred L. Templin
> >>> 	Filename        : draft-templin-intarea-rio-redirect-00.txt
> >>> 	Pages           : 5
> >>> 	Date            : 2017-01-06
> >>>
> >>> Abstract:
> >>>    The IPv6 Neighbor Discovery protocol provides a Redirect function
> >>>    allowing routers to inform hosts of a better next hop on the link
> >>>    toward the destination.  This document specifies a backward-
> >>>    compatible extension to the Redirect function to allow routers to
> >>>    include forwarding information that the source can associate with the
> >>>    next hop.
> >>>
> >>>
> >>> The IETF datatracker status page for this draft is:
> >>> https://datatracker.ietf.org/doc/draft-templin-intarea-rio-redirect/
> >>>
> >>> There's also a htmlized version available at:
> >>> https://tools.ietf.org/html/draft-templin-intarea-rio-redirect-00
> >>>
> >>>
> >>> 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.
> >>>
> >>> Internet-Drafts are also available by anonymous FTP at:
> >>> ftp://ftp.ietf.org/internet-drafts/
> >>>
> >>> _______________________________________________
> >>> I-D-Announce mailing list
> >>> I-D-Announce@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/i-d-announce
> >>> Internet-Draft directories: http://www.ietf.org/shadow.html
> >>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >>>
> >>>
> >>> --------------------------------------------------------------------
> >>> IETF IPv6 working group mailing list
> >>> ipv6@ietf.org
> >>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >>> --------------------------------------------------------------------
> >>> .
> >>>
> >