[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A comment on <draft-ksinant-v6ops-isp-analysis-00.txt>
- To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
- Subject: Re: A comment on <draft-ksinant-v6ops-isp-analysis-00.txt>
- From: Vladimir Ksinant <vladimir.ksinant@6wind.com>
- Date: Mon, 27 Oct 2003 15:42:14 +0100
- Cc: v6ops@ops.ietf.org, mikael.lind@teliasonera.com, Raffaele.Dalbenzio@TILAB.COM, Roger.Wenner@telekom.de, otter@surfnet.nl, Erik-Jan.Bos@surfnet.nl, ikejiri@byd.ocn.ad.jp, jeremy.de_clercq@alcatel.be, ikejiri@ntt.ocn.ne.jp, stuart.prevost@bt.com, dirk.ooms@alcatel.be
- References: <AC60B39EEE7320498063D37799FB82D9022B4C3F@xbe-lon-313.cisco.com>
Hello,
Please see my comments below:
"Francois Le Faucheur (flefauch)" wrote:
>
> Hello Vladimir,
>
> In section 3.3, I noticed the following:
>
> " When MPLS is already deployed in the backbone, it may be desirable
> to provide IPv6-over-MPLS connectivity. However, the problem is that
> setting up an IPv6 Label Switched Path (LSP) requires some signaling
> through the MPLS network. Currently, there is no direct mechanism to
> do this for IPv6. A workaround is to use BGP for signaling and/or
> perform IPv6-over-IPv4-over-MPLS encapsulation, as described in
> [BGPTUNNEL]. More analysis is needed on what is the right approach
> in this case.
> "
>
> Well, there actually are mechanims specified to set up IPv6 LSPs: both
> LDP and RSVP-TE specifications cover both label binding for IPv4 and
> for IPv6.
>
Yes, agreed. In the document, we did not want to cover the various ways
to provide IPv6 support on all possible underlying technologies. We also
wanted to keep it simple and not to go into too many details. The goal
of the text above was to show that when native IPv6 signalling is not
yet enabled on the MPLS network, IPv6 support can still be provided.
The text can probably be enhanced.
Thank you for your comments.
Vladimir