IETF Logo Mail Archive

Re: [dhcwg] Updating RFC 3633 with draft-ietf-dhc-dhcpv6-prefix-length-hint-issue

"Bernie Volz (volz)" <volz@cisco.com> Wed, 22 February 2017 01:18 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A40A61294BE for <dhcwg@ietfa.amsl.com>; Tue, 21 Feb 2017 17:18:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 jEiimiIEhqgV for <dhcwg@ietfa.amsl.com>; Tue, 21 Feb 2017 17:18:50 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 700C41294BF for <dhcwg@ietf.org>; Tue, 21 Feb 2017 17:18:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1086; q=dns/txt; s=iport; t=1487726330; x=1488935930; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=JsEmbxgrTubvPNvz9myQze8sIFB5xyunwGi4t7jXl6I=; b=WuFmr9QuygrDNCI1mxoCPtTYl0a8ZD+toAscG3fnomfNYDdIYSV4r/Ka R7S/cHwr5aBNhIGeiJtEC1zOQTg/T1jt3klcwlMKa6IkhFS36PyCXYnuD uq+MYln2EoePBD0NM/RGRsMFbR8fBWMmqxG6UEghRc5MyTwOUKk0w268F o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AYAQBk5qxY/5FdJa1eGQEBAQEBAQEBAQEBBwEBAQEBg1GBageNXJIWiAyNKIINhiICgnE/GAECAQEBAQEBAWIohHABAQEDATo/BQcEAgEIEQQBAQEeCQchERQJCAIEAQ0FCIlOAw0IsW6HPA2DdwEBAQEBAQEBAQEBAQEBAQEBAQEBAR2LO4E8gRWBVDaFXgWbUToBjgOEEpEYikGIYgEfOEk3UxWFPoFIdYktgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.35,191,1484006400"; d="scan'208";a="388587516"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Feb 2017 01:18:49 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v1M1InmC031382 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 22 Feb 2017 01:18:49 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 21 Feb 2017 19:18:49 -0600
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1210.000; Tue, 21 Feb 2017 19:18:48 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Erik Kline <ek@google.com>
Thread-Topic: [dhcwg] Updating RFC 3633 with draft-ietf-dhc-dhcpv6-prefix-length-hint-issue
Thread-Index: AQHSjAdpZrZhqiHmrU2X2q8zezC2gKF0ZvoA///T33A=
Date: Wed, 22 Feb 2017 01:18:48 +0000
Message-ID: <9a5b8e737dfc416dba5bbeda53854cb2@XCH-ALN-003.cisco.com>
References: <CAFx+hEMNhzShhDWxSX+JLq+KPk4HyMzdGMEWYWG6i1o+LFMb3w@mail.gmail.com> <DE41B94D-78C3-4BDE-8BA3-555D67A59E49@ericsson.com> <CAAedzxp_OtzTg+H8XqLS0x-ry7VVknwduD87AheAP4_cvpjwqA@mail.gmail.com> <7D7BC30A-FABA-43D1-BF60-4687476CE652@ericsson.com>
In-Reply-To: <7D7BC30A-FABA-43D1-BF60-4687476CE652@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.255.117]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/62d-rfOYnm8UwS05IAGya1dAfXI>
Cc: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] Updating RFC 3633 with draft-ietf-dhc-dhcpv6-prefix-length-hint-issue
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 01:18:51 -0000

And, at some point we have to draw the line as to what can be added to 3315bis or it will never finish.

I think having this as a standalone document is fine. Note that 3315bis does reference it.

- Bernie

-----Original Message-----
From: Suresh Krishnan [mailto:suresh.krishnan@ericsson.com] 
Sent: Tuesday, February 21, 2017 5:56 PM
To: Erik Kline <ek@google.com>
Cc: tianxiang li <peter416733@gmail.com>; dhcwg <dhcwg@ietf.org>; Bernie Volz (volz) <volz@cisco.com>
Subject: Re: [dhcwg] Updating RFC 3633 with draft-ietf-dhc-dhcpv6-prefix-length-hint-issue

Hi Erik,

> On Feb 21, 2017, at 12:57 AM, Erik Kline <ek@google.com> wrote:
> 
> What about folding in to 3315bis (where other 3633 info is going)?  I have no strong preference one way or the other, just asking.

<AD Hat off>That is certainly something worth considering, but I think it should be independent of this document. There are people who implement RFC3633 and it would be good if they can use this independently without needing to wait for 3315bis.

Thanks
Suresh

v2.23.0 | Report a Bug | By Email