Re: [v6ops] RFC 7084 on Basic Requirements for IPv6 Customer Edge Routers

Wuyts Carl <Carl.Wuyts@technicolor.com> Mon, 25 November 2013 12:56 UTC

Return-Path: <Carl.Wuyts@technicolor.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5AD21AD687; Mon, 25 Nov 2013 04:56:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VtT_sbibF519; Mon, 25 Nov 2013 04:56:57 -0800 (PST)
Received: from na3sys009aog129.obsmtp.com (na3sys009aog129.obsmtp.com [74.125.149.142]) by ietfa.amsl.com (Postfix) with ESMTP id 15DF01AD34C; Mon, 25 Nov 2013 04:56:54 -0800 (PST)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob129.postini.com ([74.125.148.12]) with SMTP ID DSNKUpNJAOrkBsEKutEUSisBdIazGi1Uxx0O@postini.com; Mon, 25 Nov 2013 04:56:58 PST
Received: from MOPESMAILHC02.eu.thmulti.com (141.11.100.29) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.298.1; Mon, 25 Nov 2013 13:54:39 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.1.71]) by MOPESMAILHC02.eu.thmulti.com ([141.11.100.29]) with mapi; Mon, 25 Nov 2013 13:54:40 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>, "ietf-announce@ietf.org" <ietf-announce@ietf.org>, "rfc-dist@rfc-editor.org" <rfc-dist@rfc-editor.org>
Date: Mon, 25 Nov 2013 13:54:38 +0100
Thread-Topic: [v6ops] RFC 7084 on Basic Requirements for IPv6 Customer Edge Routers
Thread-Index: Ac7ns3Z0rQMXWKIHQG2+pEydokN41wCKbm7g
Message-ID: <3135C2851EB6764BACEF35D8B495596806FB9EED1D@MOPESMBX01.eu.thmulti.com>
References: <20131122183301.9E61C75E017@rfc-editor.org>
In-Reply-To: <20131122183301.9E61C75E017@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "drafts-update-ref@iana.org" <drafts-update-ref@iana.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] RFC 7084 on Basic Requirements for IPv6 Customer Edge Routers
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Nov 2013 12:57:00 -0000

All,
I can still see it is impossible today to fully comply to this as, IMHO,  the following requirement is impossible to meet (the SHOULD part):
""
WPD-3:  The IPv6 CE router MUST be prepared to accept a delegated
           prefix size different from what is given in the hint.  If the
           delegated prefix is too small to address all of its
           interfaces, the IPv6 CE router SHOULD log a system management
           error.  [RFC6177] covers the recommendations for service
           providers for prefix allocation sizes.
""
Checking if a ia_Pd is "too small" is impossible, i.e., what is "too small" ?  What if certain changes are done after initial ia_pd ?  What .... ?

Regs
Carl


-----Original Message-----
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of rfc-editor@rfc-editor.org
Sent: vrijdag 22 november 2013 19:33
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: drafts-update-ref@iana.org; v6ops@ietf.org; rfc-editor@rfc-editor.org
Subject: [v6ops] RFC 7084 on Basic Requirements for IPv6 Customer Edge Routers

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7084

        Title:      Basic Requirements for IPv6 Customer 
                    Edge Routers 
        Author:     H. Singh, W. Beebee,
                    C. Donley, B. Stark
        Status:     Informational
        Stream:     IETF
        Date:       November 2013
        Mailbox:    shemant@cisco.com, 
                    wbeebee@cisco.com, 
                    c.donley@cablelabs.com,
                    barbara.stark@att.com
        Pages:      21
        Characters: 46569
        Obsoletes:  RFC 6204

        I-D Tag:    draft-ietf-v6ops-6204bis-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7084.txt

This document specifies requirements for an IPv6 Customer Edge (CE) router.  Specifically, the current version of this document focuses on the basic provisioning of an IPv6 CE router and the provisioning of IPv6 hosts attached to it.  The document also covers IP transition technologies.  Two transition technologies in RFC 5969's IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) and RFC 6333's Dual-Stack Lite (DS-Lite) are covered in the document.  The document obsoletes RFC 6204.

This document is a product of the IPv6 Operations Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops