Works for me. Thomas
"Hemant Singh (shemant)" <[email protected]> writes: > >-----Original Message----- > >From: Thomas Narten [mailto:[email protected]]=20 > >Sent: Tuesday, December 22, 2009 4:42 PM > >To: Hemant Singh (shemant) > >Cc: Erik Nordmark; IPv6 Maintenance WG; Wes Beebee (wbeebee) > >Subject: Re: Editorial comments on draft-ietf-6man-subnet-model-06 > >See below. > >I prefer the latter option, i.e., just adding "default router list" to > >the first sentence. > >The reason is that (going back to Section 5.2 of RFC 4861), for the > >purposes of on-link determination, one doesn't use the Neighbor > >Cache. One need only perform next-hop determination (which leads to a > >Destination Cache Entry). At that point, if the next hop address in > >the selected entry matches the address in the packet, you know its > >on-link. > Fine. Does new text below work for you? =20 > OLD TEXT > The conceptual sending algorithm of [RFC4861] defines a Prefix List and > Neighbor Cache. The combination of Prefix List and Neighbor Cache form > what many implementations consider to be the IP data forwarding table > for a host. > NEW TEXT > The conceptual sending algorithm of [RFC4861] defines a Prefix List, > Destination Cache, and Default Router List. The combination of Prefix > List, Destination Cache, and Default Router List form what many > implementations consider to be the IP data forwarding table for a host. > Thanks, > Hemant -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
