[radext] #77: Section 2

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

#77: Section 2

 "Multi-homing" is a layer 3 concept, so "multihomed at layer 2" doesn't
 parse.  RADIUS is an acronym so it is capitalized.  Recommend that this
 section be rewritten as follows:

 2.  Deployment Scenarios

    A common broadband network scenario is illustrated in Figure 1.  It
    is composed of a IP Routing Residential Gateway (RG) or host, a Layer
    2 Access-Node (e.g. a DSLAM), one or more IP Network Access Servers
    (NASes), and an AAA server.  The RG or host are expected to be multi
    homed to both NASes.  Layer 2 Connectivity between the
    host and NAS can be either via PPPoE or IP over Ethernet, and
    established dynamically.

                                                    +-----+
                                    (RADIUS server) | AAA |
                                        ...........>|     |
                                        .           +--+--+
                                        v              ^
                                    +---+---+          .
                                    |  NAS  |          .(RADIUS server)
                                    |       |          .
                                    +---+---+          v
                     +------+           |          +---+---+
      +------+       |  AN  |           |          |  NAS  |
      |  RG/ +-------|      +-----------+----------+       |
      | host |       |      |                      |       |
      +------+ (DSL) +------+      (Ethernet)      +-------+

                               Figure 1

    In this scenario the NASes may embed a DHCPv6 server to handle
    DHCPv6 requests issued by RGs/hosts, as well as acting as a
    router providing Router Advertisements.  The RADIUS server
    authenticates each RG/host and returns to the NAS attributes
    used for authorization and accounting.  These attributes
    can include a host IPv6 address to be configured via DHCPv6;
    the IPv6 address of a DNS server to configured via DHCPv6 or
    router advertisement; the name of a prefix pool to be used
    for DHCPv6 Prefix Delegation; or IPv6 routes to be announced
    to the host.

    The following sub-sections discuss how these uses in more
    detail.

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

Ticket URL: <https://wiki.tools.ietf.org/wg/radext/trac/ticket/77>
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/>