Internet DRAFT - draft-wbeebee-6man-nd-proxy-std

draft-wbeebee-6man-nd-proxy-std






Network Working Group                                           H. Singh
Internet-Draft                                                 W. Beebee
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: May 14, 2010                                  November 10, 2009


                     RFC 4389 Should be a Standard
                   draft-wbeebee-6man-nd-proxy-std-00

Abstract

   Increasingly the need for IPv6 ND Proxy [RFC4389]) to be a Standards
   Track document is growing.  During the specification of the IPv6 CE
   Router in the IETF v6ops Working Group, the IPv6 CE Router has use
   for ND Proxy to bridge disparate MAC layers LAN ports.  There is also
   the use of ND Proxy in cable broadband NBMA network for DAD and ND
   address resolution on a cable access concentrator.  Another case
   where ND Proxy is required is when one does not have enough IPv6
   address space to route.  This short note recommends that the ND Proxy
   RFC be changed to a Standards Track document.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on May 14, 2010.

Copyright Notice

   Copyright (c) 2009 IETF Trust and the persons identified as the
   document authors.  All rights reserved.



Singh & Beebee            Expires May 14, 2010                  [Page 1]

Internet-Draft                ND Proxy STD                 November 2009


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.






























Singh & Beebee            Expires May 14, 2010                  [Page 2]

Internet-Draft                ND Proxy STD                 November 2009


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Move ND Proxy to Standards Track  . . . . . . . . . . . . . . . 3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . . . 3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . . . 4
     6.2.  Informative References  . . . . . . . . . . . . . . . . . . 4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 4








































Singh & Beebee            Expires May 14, 2010                  [Page 3]

Internet-Draft                ND Proxy STD                 November 2009


1.  Introduction

   The reason IPV6 ND Proxy RFC as specified in [RFC4389] still exists
   in Experimental form is because when the RFC was completed the RFC
   still required work for SEND [RFC3971] extensions.  SEND came into
   being before the ND Proxy document, so it became a requirement for
   the new work in ND Proxy to support security extensions for SEND.
   The IETF CSI Working Group, amongst other things, was chartered to
   complete the SEND extensions for ND Proxy.  However, the work has
   still not be undertaken whereas ND Proxy is to be used in
   environments where SEND is not used


2.  Move ND Proxy to Standards Track

   The IPv6 CE Router document in
   draft-wbeebee-v6ops-ipv6-cpe-router-bis
   [I-D.wbeebee-v6ops-ipv6-cpe-router-bis] has recommended support for
   ND Proxy on the IPv6 CE Router.  A typical IPv6 CE Router is expected
   to support LAN hardware ports with disparate MAC layers and ND Proxy
   is recommended for communicating between the ports.  However, a v6ops
   document prefers not to recommend technology that is in Experimental
   form.  Further, the cable broadband IPv6 standards also recommend use
   of ND Proxy on the cable NBMA access concentrator and the same
   standards do not specify use of SEND.  As of 2007 at least two cable
   access concentrator vendors support ND Proxy.  In light of such
   facts, this document recommends that IETF move [RFC4389] from
   Experimental to Standards Track status.


3.  Security Considerations

   If a deployment chooses to use IPv6 ND Proxy without the use of SEND,
   then a deployment should be allowed to do so with security at their
   own risks.  A cable access concentrator is under the control of the
   Service Provider and if such a router supports ND Proxy, the security
   risk is limited due to an RF segment between the Service Provider and
   the cable modem and also the link is covered through the use of
   Baseline Privacy Interface security in cable standards.


4.  IANA Considerations

   None.







Singh & Beebee            Expires May 14, 2010                  [Page 4]

Internet-Draft                ND Proxy STD                 November 2009


5.  Acknowledgements

   Thanks (in alphabetical order) to Fred Baker for his suggestion for
   this note.


6.  References

6.1.  Normative References

   [RFC3971]  Arkko, J., Kempf, J., Zill, B., and P. Nikander, "SEcure
              Neighbor Discovery (SEND)", RFC 3971, March 2005.

   [RFC4389]  Thaler, D., Talwar, M., and C. Patel, "Neighbor Discovery
              Proxies (ND Proxy)", RFC 4389, April 2006.

   [RFC4861]  Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
              "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
              September 2007.

   [RFC4862]  Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
              Address Autoconfiguration", RFC 4862, September 2007.

6.2.  Informative References

   [I-D.wbeebee-v6ops-ipv6-cpe-router-bis]
              Singh, H. and W. Beebee, "IPv6 Customer Edge Router
              Recommendations(bis)",
              draft-wbeebee-v6ops-ipv6-cpe-router-bis-01 (work in
              progress), October 2009.


Authors' Addresses

   Hemant Singh
   Cisco Systems, Inc.
   1414 Massachusetts Ave.
   Boxborough, MA  01719
   USA

   Phone: +1 978 936 1622
   Email: shemant@cisco.com
   URI:   http://www.cisco.com/








Singh & Beebee            Expires May 14, 2010                  [Page 5]

Internet-Draft                ND Proxy STD                 November 2009


   Wes Beebee
   Cisco Systems, Inc.
   1414 Massachusetts Ave.
   Boxborough, MA  01719
   USA

   Phone: +1 978 936 2030
   Email: wbeebee@cisco.com
   URI:   http://www.cisco.com/










































Singh & Beebee            Expires May 14, 2010                  [Page 6]