draft-ietf-mboned-v4v6-mcast-ps-03.txt | draft-ietf-mboned-v4v6-mcast-ps-04.txt | |||
---|---|---|---|---|
MBONED Working Group C. Jacquenet | MBONED Working Group C. Jacquenet | |||
Internet-Draft M. Boucadair | Internet-Draft M. Boucadair | |||
Intended status: Informational France Telecom Orange | Intended status: Informational France Telecom Orange | |||
Expires: December 07, 2013 Y. Lee | Expires: March 10, 2014 Y. Lee | |||
Comcast | Comcast | |||
J. Qin | J. Qin | |||
Cisco Systems | Cisco Systems | |||
T. Tsou | T. Tsou | |||
Huawei Technologies (USA) | Huawei Technologies (USA) | |||
Q. Sun | Q. Sun | |||
China Telecom | China Telecom | |||
June 05, 2013 | September 06, 2013 | |||
IPv4-IPv6 Multicast: Problem Statement and Use Cases | IPv4-IPv6 Multicast: Problem Statement and Use Cases | |||
draft-ietf-mboned-v4v6-mcast-ps-03 | draft-ietf-mboned-v4v6-mcast-ps-04 | |||
Abstract | Abstract | |||
This document discusses issues and requirements raised by IPv4-IPv6 | This document discusses issues and requirements raised by intra- | |||
multicast interconnection and co-existence scenarios. It also | domain IPv4-IPv6 multicast interconnection and co-existence | |||
discusses various multicast use cases which may occur during IPv6 | scenarios. It also discusses various multicast use cases which may | |||
transitioning. | occur during IPv6 transitioning. | |||
Status of This Memo | Status of This Memo | |||
This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
This Internet-Draft will expire on December 07, 2013. | This Internet-Draft will expire on March 10, 2014. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2013 IETF Trust and the persons identified as the | Copyright (c) 2013 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
skipping to change at page 3, line 17 | skipping to change at page 3, line 17 | |||
example, the observed evolution of ADSL broadband access | example, the observed evolution of ADSL broadband access | |||
infrastructures from a service-specific, multi-PVC (Permanent Virtual | infrastructures from a service-specific, multi-PVC (Permanent Virtual | |||
Circuit) scheme towards a "service-agnostic", single PVC scheme, | Circuit) scheme towards a "service-agnostic", single PVC scheme, | |||
assumes the allocation of a globally unique IPv4 address on the WAN | assumes the allocation of a globally unique IPv4 address on the WAN | |||
(Wide Area Network) interface of the CPE (Customer Premises | (Wide Area Network) interface of the CPE (Customer Premises | |||
Equipment), or to a mobile terminal), whatever the number and the | Equipment), or to a mobile terminal), whatever the number and the | |||
nature of the services the customer has subscribed to. | nature of the services the customer has subscribed to. | |||
Likewise, the global IPv4 address depletion encourages the | Likewise, the global IPv4 address depletion encourages the | |||
development of IPv6 receivers while contents may very well remain | development of IPv6 receivers while contents may very well remain | |||
IPv4-formatted. There is therefore a need to make sure such IPv6 | IPv4-formatted, i.e., sourced by an IPv4 application. There is | |||
receivers can access IPv4-formatted contents during the transition | therefore a need to make sure such IPv6 receivers can access | |||
period. | IPv4-formatted contents during the transition period. | |||
During the transition period, the usage of the remaining global IPv4 | During the transition period, the usage of the remaining global IPv4 | |||
address blocks will have to be rationalized for the sake of IPv4 | address blocks will have to be rationalized for the sake of IPv4 | |||
service continuity. The current state-of-the-art suggests the | service continuity. The current state-of-the-art suggests the | |||
introduction of NAT (Network Address Translation) capabilities | introduction of NAT (Network Address Translation) capabilities | |||
(generally denoted as CGN, for Carrier-Grade NAT) in providers' | (generally denoted as CGN, for Carrier-Grade NAT) in providers' | |||
networks, so that a global IPv4 address will be shared between | networks, so that a global IPv4 address will be shared between | |||
several customers. | several customers. | |||
As a consequence, CPE or mobile UE (User Equipment) devices will no | As a consequence, CPE or mobile UE (User Equipment) devices will no | |||
End of changes. 6 change blocks. | ||||
11 lines changed or deleted | 11 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |