Re: [dhcwg] 3315bis use of "requesting router" term
"Bernie Volz (volz)" <volz@cisco.com> Thu, 24 November 2016 03:47 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 1292E12943A; Wed, 23 Nov 2016 19:47:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.018
X-Spam-Level:
X-Spam-Status: No, score=-16.018 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=-1.497, 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 ZpidWE8noFD2; Wed, 23 Nov 2016 19:47:19 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42C2C126D73; Wed, 23 Nov 2016 19:47:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3931; q=dns/txt; s=iport; t=1479959239; x=1481168839; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=qCGEOK7w7SNQxhikDdBSxBUWoAcqr1u5cm/+hfByMiU=; b=SeUa9v/OUoMZO5urA37LTz0SRD5X0aFv8A2Gu4sRnOwIErAIVX/W+G9K ptoFfhP9vZ9qIZk2jiRA6iKU7IO18v0zMAtIDX1U392yx0UNmAU1t9Gr8 Vu8vM2uNM2prw4gT4rD9G49CyjJQHZB82m5ag+mKWinIX6XgwzF3G/uKP 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C5AQBUYjZY/4wNJK1eGwEBAQMBAQEJAQEBgzgBAQEBAR9YgQKNQKZvhR+CCCqFdwKBfD8UAQIBAQEBAQEBYiiEaQEBAgJ5EAIBCAQxCgcyFBECBA4FiG0OsBeLWAEBAQEBAQEBAQEBAQEBAQEBAQEBARcFiDsIglaEOYNBgjAFmk8BhkaKOZAxjWqECwEeNy4NWSwBAYUacgGIRgEBAQ
X-IronPort-AV: E=Sophos;i="5.31,690,1473120000"; d="scan'208,217";a="175127062"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 24 Nov 2016 03:47:18 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id uAO3lIep031372 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 24 Nov 2016 03:47:18 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 23 Nov 2016 21:47:17 -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; Wed, 23 Nov 2016 21:47:17 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Lorenzo Colitti <lorenzo@google.com>
Thread-Topic: 3315bis use of "requesting router" term
Thread-Index: AQHSRfbGOHYDRK59ekarOL73Bal9q6DnfvlO
Date: Thu, 24 Nov 2016 03:47:17 +0000
Message-ID: <C1EA7398-C196-46F9-8339-4EA794A19298@cisco.com>
References: <CAKD1Yr0ZtfKOe9Ut7hGpr_f=ahOSEEB8VAxmUk+rRu5uPoC4+w@mail.gmail.com>
In-Reply-To: <CAKD1Yr0ZtfKOe9Ut7hGpr_f=ahOSEEB8VAxmUk+rRu5uPoC4+w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_C1EA7398C19646F983394EA794A19298ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/kuus4YYjv2JkTd19urSoB6Eq7rw>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "dhcpv6bis@ietf.org" <dhcpv6bis@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] 3315bis use of "requesting router" term
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: Thu, 24 Nov 2016 03:47:21 -0000
See the 06 version. This ticket has been dealth with we believe. - Bernie (from iPad) On Nov 23, 2016, at 9:02 PM, Lorenzo Colitti <lorenzo@google.com<mailto:lorenzo@google.com>> wrote: On Mon, Oct 31, 2016 at 12:50 PM, Bernie Volz (volz) <volz@cisco.com<mailto:volz@cisco.com>> wrote: This version does NOT yet have ALL of the WGLC comments received over the summer addressed - there were almost 300 of the them and we are probably close to 3/4 done. (We also have a few issues in the issues tracker let to resolve - see https://trac.tools.ietf.org/group/dhcpv6bis/report/1.) Hi, (Apologies if this was mentioned in Seoul - I couldn't make it due to a conflict.) I looked at the open issues discussion slides<https://www.ietf.org/proceedings/97/slides/slides-97-dhc-dhcpv6bis-open-issues-discussion-01.pdf> and I saw it wasn't mentioned, so I thought I'd ask: what's the status of ticket #167<https://wiki.tools.ietf.org/group/dhcpv6bis/ticket/167> to change the term "requesting router" to "client"? Is this one of the issues the authors were planning to resolve? Since the ticket was opened, RFC 7934 was published as BCP and one of the options it recommends is to use DHCPv6 PD to assign prefixes to hosts, so I think this should be resolved before publication. Cheers, Lorenzo
- [dhcwg] 3315bis use of "requesting router" term Lorenzo Colitti
- Re: [dhcwg] 3315bis use of "requesting router" te… Bernie Volz (volz)
- Re: [dhcwg] 3315bis use of "requesting router" te… Lorenzo Colitti