Signaling Protocol for Access Service Network using LDP draftmatsudal2vpnaccessserviceprotocol00'txt

1
Signaling Protocol for Access Service Network
using LDP (draft-matsuda-l2vpn-access-service-pro
tocol-00.txt)Tetsushi MatsudaInformation
Technology RD CenterMitsubishi Electric
Corporationfor IETF 59th meeting on March 3, 2004
2
What do I call Access Service Network?

• Basically Network Access Providers network
• A subscriber can specify the ISP to connect to by
  authentication information (usually NAI) that the
  subscriber presents when attaching to an Access
  Service Network
• L2TP and PPPoEADSL is commonly used to implement
  a Broadband Access Service Network today

RADIUS Server
RADIUS Server

L2TP Network Server

ISP1

LAC
Subscriber1
L2TP
PPPoE
RADIUS Server
ADSL

Access Service Network
ISP2
3
Brief overview of the draft

• The draft proposes to implement an Access Service
  Network which allows a subscriber to connect to
  an ISP by authenticating with IEEE 802.1X as a
  special kind of VPLS
• It is desirable not to forward broadcast/multicast
  frames between subscribers (PWs) in an Access
  Service Network for security
• Bridge function exists only in Network Server
• Network Access Concentrator maps a port attaching
  to a subscriber to a PW between a Network Access
  Concentrator and a Network Server (simlar to
  VPWS)

RADIUS Server
RADIUS Server
Network Server

Subscriber1
Network Access Concentrator

ISP1
Pseudo Wire
Bridge Function
802.1X
Subscriber2
Do not forward broadcast/multicast frames between
PWs
Access Service Network
4
Brief overview of the draft (cont.)

• Network Access Concentrator determines Network
  Server with which to set up PWs by querying a
  RADIUS server in Access Service Network using NAI
  as a key
• Use LDP signaling discussed in PWE3 WG to set up
  pseudo wires between a Network Access
  Concentrator and a Network Server
• Defines a format of Generalize ID FEC for Access
  Service Network application (SAII and TAII, no
  AGI)
• QoS information can be specified when
  establishing PWs
• Transport QoS information for each subscriber in
  RADIUS Access-Accept message returned by RADIUS
  server in ISP
• Transport QoS information for each subscriber in
  LDP Label Mapping message

5
Merit of the approach

• Reduced overhead of packet encapsulation format
  compared to L2TP
• Use Pseudo Wire to transport Ethernet frames
  (MPLS VC label and tunnel label)
• 38byte for L2TP -gt 8byte for label stack (18byte
  Ehternet Encap.)
• Enable QoS service for each subscriber
• Implementation of QoS such as Minimum Guaranteed
  Bandwidth is made easier by using LSP as PSN
  tunnel

6
I Hope this is considered to be a WG item.
Comments are welcome.
Thank you!