Re: [dhcwg] Call for Agenda Items for IETF-89 (London)

"Bernie Volz (volz)" <volz@cisco.com> Mon, 20 January 2014 14:57 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDFE91A0198 for <dhcwg@ietfa.amsl.com>; Mon, 20 Jan 2014 06:57:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level:
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 eQ19iz-CVNUM for <dhcwg@ietfa.amsl.com>; Mon, 20 Jan 2014 06:57:30 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by ietfa.amsl.com (Postfix) with ESMTP id AD6A01A0197 for <dhcwg@ietf.org>; Mon, 20 Jan 2014 06:57:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1763; q=dns/txt; s=iport; t=1390229851; x=1391439451; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=DclutZ0F5hDK/IgFgkESGKc872Zz7Cl1jZUt5xzDw5s=; b=cOyhdDb25+OrOoE+cbyyccIuUF3cinHYjVFxtAtlIb/cvtSzFWP4y/F7 ClXwwlXGnAB8aRFgw5USLjmUBEJ42+tcSTj23ZZ+3ZNZ08UTtMtQec/1X lt2d/siVn8XGbDnAamUhEs9ttR3uefqMbQTJep6Xa52M3Cq+HWL+wwss1 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwFAA053VKtJV2Z/2dsb2JhbABZgws4Vrs8gQ8WdIIlAQEBAwEBAQEaURcEAgEIEQQBAQEKHQcnCxQJCAEBBAESCAGHdAgNw1sXjisjMwUGgx6BFASJD4stlX6DLYIq
X-IronPort-AV: E=Sophos;i="4.95,691,1384300800"; d="scan'208";a="14134369"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-2.cisco.com with ESMTP; 20 Jan 2014 14:57:30 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0KEvUJs025142 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 20 Jan 2014 14:57:30 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0123.003; Mon, 20 Jan 2014 08:57:30 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] Call for Agenda Items for IETF-89 (London)
Thread-Index: Ac8QicsdauE7TMjdQ2Oym9UwCvtTNwFke8IAAAA2Y4AAC4hEkA==
Date: Mon, 20 Jan 2014 14:57:30 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE2AA2A@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1AE1B259@xmb-rcd-x04.cisco.com> <52DD2E70.90203@gmail.com> <52DD2FDD.5090805@gmail.com>
In-Reply-To: <52DD2FDD.5090805@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.247.199]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] Call for Agenda Items for IETF-89 (London)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 20 Jan 2014 14:57:32 -0000

Yes, but RFC 3633 does and so likely we will need that definition once we merge the two into a single DHCPv6 specification.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Alexandru Petrescu
Sent: Monday, January 20, 2014 9:17 AM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Call for Agenda Items for IETF-89 (London)

Le 20/01/2014 15:10, Tomek Mrugalski a écrit :
> On 13.01.2014 19:03, Bernie Volz (volz) wrote:
>> The London IETF is not that far off (Mar 2-7). See 
>> http://www.ietf.org/meeting/89/index.html for more details, including 
>> venue information and important dates.
>>
>> Thus, we are starting the call for agenda items. The co-chairs will 
>> finalize the agenda about two weeks before the meeting and will give 
>> priority to items as follows (in this order):
> It is somewhat odd, but it's been a week already and we haven't 
> received a single slot request yet.
>
> With my chair hat off, I'd like to request 20 minutes slot for the 
> RFC3315-bis status update.
>
> Topic: RFC3315bis work
> Presenter: Tomek Mrugalski
> I-D: draft-dhcwg-dhc-rfc3315bis-00
> Time: 20 minutes

YEs I agree with this request.

Someone and I made some comment recently in v6ops about the contents of RFC3315, with respect to the definition of term 'prefix length' yet never used.

And of course, I suppose many are curious about the advancement of this.

Alex

>
> Tomek
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg