In Prague (IETF-99), there was a hum for adoption after a long and vivid 
discussion and the hum was in favor of adoption of this I-D as a intarea 
document: large interest, running code, privacy section to be enhanced though, 
critical for other WG and possible a dedicated WG later.

Juan-Carlos and Wassim, how can we proceed to get this I-D adopted as a WG 

Thanks in advance


On 28/07/17 09:02, "Pierre Pfister" <> wrote:

    Hello all,
    We have just published a new version of the intarea-provisioning-domains 
    This new version includes changes based on the feedback received during the 
IETF hackathon, the int-area session, as well as in a few other working groups 
such as capport and 6man.
    You can find major changes with respect to the previous version in the 
changelog section, in the appendix.
    Since the room hummed in favour of adopting this draft during the last IETF 
int-area session, we would also like to kindly request the chairs to confirm 
the adoption based on this new version.
    - Pierre
    > A new version of I-D, draft-bruneau-intarea-provisioning-domains-02.txt
    > has been successfully submitted by Pierre Pfister and posted to the
    > IETF repository.
    > Name:             draft-bruneau-intarea-provisioning-domains
    > Revision: 02
    > Title:            Discovering Provisioning Domain Names and Data
    > Document date:    2017-07-28
    > Group:            Individual Submission
    > Pages:            20
    > URL:   
    > Status:
    > Htmlized:
    > Htmlized:
    > Diff:  
    > Abstract:
    >   An increasing number of hosts and networks are connected to the
    >   Internet through multiple interfaces, some of which may provide
    >   multiple ways to access the internet by the mean of multiple IPv6
    >   prefix configurations.
    >   This document describes a way for hosts to retrieve additional
    >   information about their network access characteristics.  The set of
    >   configuration items required to access the Internet is called a
    >   Provisioning Domain (PvD) and is identified by a Fully Qualified
    >   Domain Name (FQDN).  This identifier, retrieved using a new Router
    >   Advertisement (RA) option, is associated with the set of information
    >   included within the RA and may later be used to retrieve additional
    >   information associated with the PvD by the mean of an HTTP request.
    > Please note that it may take a couple of minutes from the time of 
    > until the htmlized version and diff are available at
    > The IETF Secretariat

Int-area mailing list

Reply via email to