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

The idea is that a unique /64 is given to each of the LAN interfaces.  If
there's not enough delegated address space, a system management error
SHOULD be logged (the reason it's a SHOULD is that some boxes may not have
a web-interface/console to log to).  The document doesn't cover the case
where you add LAN interfaces to the box - but you could, in principle,
follow the same logic there as well - and log an error message.

- Wes

On 11/25/13 7:54 AM, "Wuyts Carl" <Carl.Wuyts@technicolor.com> wrote:

>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
>_______________________________________________
>v6ops mailing list
>v6ops@ietf.org
>https://www.ietf.org/mailman/listinfo/v6ops