Re: [dhcwg] Reminder - WGLC on draft-ietf-dhc-rfc3315bis-05 - respond by August 22nd

"Yogendra Pal (yogpal)" <> Mon, 22 August 2016 21:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D4A6312D1D2 for <>; Mon, 22 Aug 2016 14:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -15.069
X-Spam-Status: No, score=-15.069 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AhB3hgXpBP3W for <>; Mon, 22 Aug 2016 14:36:34 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3FBFA12D0CF for <>; Mon, 22 Aug 2016 14:36:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=21163; q=dns/txt; s=iport; t=1471901794; x=1473111394; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=MiekwsuseGwyRwVf+gha8ZFt5Ol/9omPNMtv5iE0OE8=; b=W79G+HTkcf0MBMbKMIRxCUva9F2legNpTgI1nd6pbQMrzY2WBmckD8qw /XyoA1ovzkJiDDfM3x3/3P1bb5VMskQ66uXNWtd3bwkQ4CbruQE1LrRQl 10G8HcXYa1Oe21CgO/BrT9aXU1E3K0qckL8Cn36V0kvfl1X0FnsT2JQDz E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.28,562,1464652800"; d="scan'208,217";a="314129498"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 22 Aug 2016 21:36:32 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id u7MLaWjX032655 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <>; Mon, 22 Aug 2016 21:36:32 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 22 Aug 2016 16:36:32 -0500
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Mon, 22 Aug 2016 16:36:32 -0500
From: "Yogendra Pal (yogpal)" <>
To: "" <>
Thread-Topic: [dhcwg] Reminder - WGLC on draft-ietf-dhc-rfc3315bis-05 - respond by August 22nd
Thread-Index: AQHR/LoY9T7ZBx8uzkKBch8b7ECzrKBWMQyA
Date: Mon, 22 Aug 2016 21:36:32 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_D3E16B921604Dyogpalciscocom_"
MIME-Version: 1.0
Archived-At: <>
Cc: "Bernie Volz (volz)" <>
Subject: Re: [dhcwg] Reminder - WGLC on draft-ietf-dhc-rfc3315bis-05 - respond by August 22nd
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 22 Aug 2016 21:36:37 -0000


  *   Been a very lengthly document, quick read of version (05) and I have few comments.
  *   Appreciate efforts of all the authors bringing this document into collating form of rfc. 3315, prefix delegation (3633) and


  *   Strongly support moving forward into standards.

Comments below [YP]:


>>delegating router can delegate prefixes to requesting routers

[YP]Can we make document reflect the DHCPv6 client/server/relay

instead of routers. Since Delegating entity can be any device in n/w.


>>Understanding a protocol which definition is

>>spread between large number of documents may be cumbersome.

[YP]Could not connect with this text, is there some typo or can be rephrased ?


>>the client can obtain configuration information

[YP]Not consistent with text “other configuration information” in many

places in this section. Can be consistent w/ text “other configuration information”.

>>This message includes an indication that the client is

>>willing to accept an immediate Reply message from the server.

[YP] Can we update above text to:

This message includes an indication (i.e. Rapid Commit option (see

Section 20.14<>) that the client is willing to accept an

immediate Reply message from the server.


>>If the requesting router assigns a delegated prefix to a link to

>>which the router is attached, and begins to send router

>>advertisements for the prefix on the link, the requesting router MUST

>>set the valid lifetime in those advertisements to be no later than

>>the valid lifetime specified in the IA_PD Prefix option.  A

>>requesting router MAY use the preferred lifetime specified in the

>>IA_PD Prefix option.

[YP] Addition of following text for adding operational experience to above:

Operator MUST configure requesting router with periodic RA lifetime to be less than

preferred lifetime so that renewed prefix(s) can be advertised within limits and there

is no operational traffic drop experience to subscribers.

Regards, Yogendra

From: Bernie Volz (volz) <<>>
Date: Mon, Aug 15, 2016 at 6:56 PM
Subject: [dhcwg] Reminder - WGLC on draft-ietf-dhc-rfc3315bis-05 - respond by August 22nd
To: dhcwg <<>>


Just a friendly reminder that this (extended) WGLC is scheduled to end in a week (August 22nd).

Thanks much to all those that have responded so far!!

- Bernie

-----Original Message-----
From: dhcwg [<>] On Behalf Of Bernie Volz (volz)
Sent: Monday, August 08, 2016 9:38 AM
To: dhcwg <<>>
Subject: [dhcwg] Extended - WGLC on draft-ietf-dhc-rfc3315bis-05 - respond by August 22nd


In discussions with Ralph and Tomek, we have decided to extend the WGLC for this document by 2 weeks. So comments are due Monday 8/22.

Thanks to all those that have sent review comments so far!!!

- Bernie (for Ralph and Tomek)

-----Original Message-----
From: dhcwg [<>] On Behalf Of Bernie Volz (volz)
Sent: Thursday, July 28, 2016 11:14 AM
To: dhcwg <<>>
Subject: [dhcwg] Reminder - WGLC on draft-ietf-dhc-rfc3315bis-05 - respond by August 8th


Just a reminder about this WGLC ... please review and respond by August 8th. For a reminder as to the goals and key areas of change, please see

As a reminder, the following people agreed to review during WGLC:


    Volunteers for review: Ted Lemon, Bernie Volz, Mohammed Boucadair, Tim Winters,
    Tim Chown, Francis Dupont, Paul Ebersman
    Co-authors (who are supposed to review without explicitly voluneering): Bernie Volz,
    Sheng Jiang, Marcin Siodelski,
    Ian - I also volunteered to review

And, at IETF-96:

   Yogendra Pal volunteered to review the draft.

Thanks much!

- Bernie

-----Original Message-----
From: dhcwg [<>] On Behalf Of Tomek Mrugalski
Sent: Friday, July 08, 2016 1:03 PM
To: dhcwg <<>>
Subject: [dhcwg] WGLC on draft-ietf-dhc-rfc3315bis-05 - respond by August 8th

Hi all,

So the day finally has come. Authors working on RFC3315bis believe that after over two years of work, this document is ready for working group last call. This call initiates the working group last call on
draft-ietf-dhc-rfc3315bis-05 [1]. Since this is a large document (130+ pages), there's upcoming meeting and a holiday period, chairs decided to do an extended last call that will last 4 weeks. Please post your comments by August 8th.

We do have a slot reserved for this work in Berlin. We will present the overview of the document (some areas are organized differently than original 3315), go over the most important changes and will discuss any comments raised to date.

If you would like to review more important changes, looking at appendices A anb B seems like a good place to start. If you like to see the list of tickets addressed, see [2]. Many smaller issues were discussed on dhcpv6bis mailing list [3].

This is the most important document the DHC working group is currently working on. Please review it thoroughly. Since both co-chairs are also co-authors, our shepherd, Ralph Droms, will determine consensus and wrap up the WGLC. Thank you Ralph for stepping up and helping with this!


Bernie & Tomek

dhcwg mailing list<>