Re: [radext] #71: Section 2.3 and 3.3

["radext issue tracker" <trac+radext@zinfandel.tools.ietf.org>]

#71: Section 2.3 and 3.3


Comment(by bernard_aboba@â):

 It seems to me that we want to enable use of routes in advertisements as
 well as in routing protocols, and possibly both at once.  RFC 3162 defines
 Framed-IPv6-Route, and the intent there was to enable inclusion in router
 advertisements, as well as potential redistribution in IGPs, depending on
 the value of Framed-Routing.  The question is how it was implemented.

-- 
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@â            |       Owner:  wdec@â        
     Type:  defect                     |      Status:  assigned      
 Priority:  major                      |   Milestone:  milestone1    
Component:  ipv6-access                |     Version:  1.0           
 Severity:  In WG Last Call            |    Keywords:                
---------------------------------------+------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/71#comment:2>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>