datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

6to4 Provider Managed Tunnels
draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-07

RFC
Document Stream: ISE
Last updated: 2012-07-10
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup

IESG State: RFC 6732
On agenda of 2012-07-05 IESG telechat
Responsible AD: Ron Bonica
IESG Note: ISE Submission
Send notices to: victor.kuarsingh@gmail.com, yiu_lee@cable.comcast.com, Olivier@juniper.net, draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org, rfc-ise@rfc-editor.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-kuarsingh-v6ops-6to4-provider-managed-tunnel.

Abstract:
6to4 Provider Managed Tunnels (6to4-PMT) provide a framework that can help manage 6to4 tunnels operating in an anycast configuration. The 6to4-PMT framework is intended to serve as an option for operators to help improve the experience of 6to4 operation when conditions of the network may provide sub-optimal performance or break normal 6to4 operation. 6to4-PMT supplies a stable provider prefix and forwarding environment by utilizing existing 6to4 relays with an added function of IPv6 Prefix Translation. This operation may be particularly important in NAT444 infrastructures where a customer endpoint may be assigned a non-RFC1918 address, thus breaking the return path for anycast-based 6to4 operation. 6to4-PMT has been successfully used in a production network, implemented as open source code, and implemented by a major routing vendor. This document is not an Internet Standards Track specification; it is published for informational purposes.

Authors:
Victor Kuarsingh <victor.kuarsingh@gmail.com>
Yiu Lee <yiu_lee@cable.comcast.com>
Olivier Vautrin <Olivier@juniper.net>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)