RE: L2VPNs must not be IP(v4)-only

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Correct.

One addition: Giles Heron from Tellabs
is already working on IPv6 part of this draft.

/himanshu

> -----Original Message-----
> From: Shane Amante [mailto:shane@xxxxxxxxxxxxxxx]
> Sent: Thursday, August 17, 2006 9:29 AM
> To: Pekka Savola
> Cc: l2vpn@xxxxxxxx; ietf@xxxxxxxx
> Subject: Re: L2VPNs must not be IP(v4)-only
> 
> 
> Pekka,
> 
> This topic has come up in the past -- the last time I recall 
> it being a 
> significant issue was IETF 63 in Paris, France.  On multiple 
> occasions 
> since then we have asked for volunteers with IPv6 expertise to help 
> complete the IPv6 bits of this I-D.  Unfortunately, we have gotten 
> little to no response.   Do you wish to help out with this?  
> Or, can you 
> provide a pointer to folks in the IPv6 world that can take a look at 
> this doc and help out?
> 
> Thanks,
> 
> -shane
> 
> 
> Pekka Savola wrote:
> > On Wed, 16 Aug 2006, Internet-Drafts@xxxxxxxx wrote:
> >> A New Internet-Draft is available from the on-line Internet-Drafts
> >> directories.
> >> This draft is a work item of the Layer 2 Virtual Private Networks 
> >> Working Group of the IETF.
> >>
> >>     Title        : ARP Mediation for IP Interworking of Layer 2 VPN
> >>     Author(s)    : H. Shah, et al.
> >>     Filename    : draft-ietf-l2vpn-arp-mediation-07.txt
> >>     Pages        : 21
> >>     Date        : 2006-8-16
> > ...
> >> The VPWS service [L2VPN-FRM] provides point-to-point connections
> >> between pairs of Customer Edge (CE) devices.  It does so by
> >> binding two Attachment Circuits (each connecting a CE device
> >> with a Provider Edge, PE, device) to a pseudowire (connecting
> >> the two PEs).  In general, the Attachment Circuits must be of
> >> the same technology (e.g., both Ethernet, both ATM), and the
> >> pseudowire must carry the frames of that technology.  However,
> >> if it is known that the frames' payload consists solely of IP
> >> datagrams, it is possible to provide a point-to-point connection
> >> in which the pseudowire connects Attachment Circuits of
> >> different technologies. This requires the PEs to perform a
> >> function known as "ARP Mediation". ARP Mediation refers to the
> >> process of resolving Layer 2 addresses when different resolution
> >> protocols are used on either Attachment Circuit. The methods
> >> described in this document are applicable even when the CEs run
> >> a routing protocol between them, as long as the routing protocol
> >> runs over IP.
> > 
> > 
> > The document says,
> > 
> >      10. IPV6 Considerations
> > 
> >      The support for IPV6 is not addressed in this draft and is for
> >      future study.
> > 
> > This needs to be addressed throughout the document.
> > 
> > The whole point of L2VPNs (IMHO) is that it's agnostic of 
> what protocols 
> > users run above L2.  Users depend on a transparent L2 
> service model and 
> > this model breaks that assumption.
> > 
> 
> 

_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]