From volz@cisco.com Wed Jan 1 14:32:47 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60B071AD66E for ; Wed, 1 Jan 2014 14:32:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.038 X-Spam-Level: X-Spam-Status: No, score=-10.038 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, RP_MATCHES_RCVD=-0.538, 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 fwDQfqMjixI4 for ; Wed, 1 Jan 2014 14:32:45 -0800 (PST) Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id 9538D1AD628 for ; Wed, 1 Jan 2014 14:32:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5544; q=dns/txt; s=iport; t=1388615559; x=1389825159; h=from:to:subject:date:message-id:mime-version; bh=juhFCgeRwoySOAJ+Q/Qw6kBmvme0R2JOKfdlr3mVdXA=; b=g7+7I4ILPTSQHIo4Y+akSfrNL10qS/OXPEzDY78xBrkoy3xvBft4p8X9 8/pu7dqIi/6OpyA3OAxTwHNUqfZzskpgqhGaCBLFUk1qxbIqx+AsbY3Gp N9g0ETIB38WNRTzmQ+flcZweUDcgJSw1TCiCXPEYlMUCi5f4Y/JblHsq8 s=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqwFAEOWxFKtJV2Z/2dsb2JhbABYgkdEOFW5H4EWFnSCJwEELV4BKlYmAQQbh3wNm1CoURMEjSOBSS2DLoETBKorgy2CKg X-IronPort-AV: E=Sophos;i="4.95,587,1384300800"; d="scan'208,217";a="9998552" Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-8.cisco.com with ESMTP; 01 Jan 2014 22:32:38 +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 s01MWcGT029779 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Wed, 1 Jan 2014 22:32:38 GMT Received: from xmb-rcd-x04.cisco.com ([169.254.8.230]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0123.003; Wed, 1 Jan 2014 16:32:38 -0600 From: "Bernie Volz (volz)" To: "dhcpv6bis@ietf.org" Thread-Topic: RFC 3315 bis Thread-Index: Ac8HQSK6Z8i1a4c8QHqNkRVp7NmzdQ== Date: Wed, 1 Jan 2014 22:32:37 +0000 Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE02AB6@xmb-rcd-x04.cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.86.255.139] Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1AE02AB6xmbrcdx04ciscoc_" MIME-Version: 1.0 Subject: [Dhcpv6bis] RFC 3315 bis X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jan 2014 22:32:47 -0000 --_000_489D13FBFA9B3E41812EA89F188F018E1AE02AB6xmbrcdx04ciscoc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable FYI - I think I have addressed the remaining formatting issues with RFC 331= 5 bis. The latest is in https://github.com/dhcwg/rfc3315bis/blob/master/rfc3315bis= .xml and https://github.com/dhcwg/rfc3315bis/blob/master/rfc3315bis.txt. - Bernie --_000_489D13FBFA9B3E41812EA89F188F018E1AE02AB6xmbrcdx04ciscoc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

FYI – I think I have addressed the remaining f= ormatting issues with RFC 3315 bis.

 

The latest is in https://github.com/dhcwg/rfc3315bis/blob/master/rfc3315bis.xml and https://github.com/dhcwg/rfc3315bis/blob/master/rfc3315bis.txt.

 

-     &= nbsp;    Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E1AE02AB6xmbrcdx04ciscoc_-- From volz@cisco.com Mon Jan 6 14:50:30 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03C521AE2A4 for ; Mon, 6 Jan 2014 14:50:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.038 X-Spam-Level: X-Spam-Status: No, score=-15.038 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, RP_MATCHES_RCVD=-0.538, 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 xLOLyY7A950u for ; Mon, 6 Jan 2014 14:50:27 -0800 (PST) Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 6F7FF1AE28D for ; Mon, 6 Jan 2014 14:50:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17251; q=dns/txt; s=iport; t=1389048619; x=1390258219; h=from:to:subject:date:message-id:mime-version; bh=NVQ4KkhS1r6xn7DB3WcXKliV20n6nPPHceiZ+NvoDR4=; b=OW5v0B3lbe8jzFjUxwTAMWi3ZEiyBbzw+eUQhn5WZrDeIZjSIFtRRHlY LY85TRm45kzcoZnMX8wS/vHvgPkDqy6YnjObtxzRAfzyuCEktb5Nf1g13 Ax2VHpzzsfta3ojhBtQxJSRNY+XShV8OjNf1IgZJ+fREpN2UgelqSNh94 k=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuUHAHQyy1KtJV2a/2dsb2JhbABYgkdEOFWwd4hVgQ8WdIInAQQtXgEqViYBBBsXh2UNmj+pAReOShQtgy+BEwSZR5Blgy2CKg X-IronPort-AV: E=Sophos;i="4.95,614,1384300800"; d="scan'208,217";a="295609352" Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-5.cisco.com with ESMTP; 06 Jan 2014 22:50:18 +0000 Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s06MoIYl010702 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 6 Jan 2014 22:50:18 GMT Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0123.003; Mon, 6 Jan 2014 16:50:17 -0600 From: "Bernie Volz (volz)" To: "dhcpv6bis@ietf.org" Thread-Topic: Publish 3315bis, issue tracker, another meeting? Thread-Index: Ac8LMYUI34DxbQVfRYiRpDhWxSS0AQ== Date: Mon, 6 Jan 2014 22:50:16 +0000 Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE0A6E0@xmb-rcd-x04.cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.86.247.9] Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1AE0A6E0xmbrcdx04ciscoc_" MIME-Version: 1.0 Subject: [Dhcpv6bis] Publish 3315bis, issue tracker, another meeting? X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jan 2014 22:50:30 -0000 --_000_489D13FBFA9B3E41812EA89F188F018E1AE0A6E0xmbrcdx04ciscoc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi: Several points: 1. Publishing initial RFC 3315bis before modifications. 2. Open issue tracker tickets for 3315/3633 bis issues. 3. Next meeting? Wed Jan 15 @ 0800 US EST? 1. Publishing initial RFC 3315bis before modifications: I did some additional work on the RFC3315 bis document and plan to publish = it as draft-dhcwg-dhc-rfc3315bis-00. You can see the "final" versions at: https://github.com/dhcwg/rfc3315bis/blob/master/rfc3315bis.txt https://github.com/dhcwg/rfc3315bis/blob/master/rfc3315bis.xml For now, I placed the original authors onto the document. As Ted and Ralph = will be notified of this draft submission, I explained to them what we are = doing and will see if they have any comments/suggestions before I post it. Note that we won't publish the converted 3633 because we don't intend to ha= ve a 'bis' version of that; instead that material will be merged into 3315.= I'm not sure where the 3633 xml conversion stands; perhaps it is as comple= te as it needs to be? 2. Open issue tracker tickets for 3315/3633 bis issues: A few tickets were opened at http://trac.tools.ietf.org/group/dhcpv6bis for= errata and some other items. I know I most go through my email to locate o= ther issues I've captured over the years, and hopefully others will do the = same. So, this is just a friendly reminder to do that. Note: Best to open one ticket per issue as this will make it easier to trac= k and mark complete. This is especially important for any items that may n= eed some discussion before being 'accepted' (pre-existing approved errata, = for example, are OK to list as one though even then having them separate me= ans they don't all need to be done 'at once'). 3. Next meeting? How about we have another WebEx meeting Wednesday, Jan 15 @ 0800 US EST (sa= me time as the last meeting) to determine next steps. By then, we should ha= ve RFC3315bis and RFC3633bis in XML form and most issues tracked. And, that= means to start work on updating the 3315bis document (based on tickets) an= d 3633 changes and how to best do this. Let me know if you are OK with the Wed Jan 15 meeting. Also, just in case t= hat date doesn't work well, let me know how Wed Jan 22nd works as an altern= ate. (Note that I will not be available from 1/24-2/8.) - Bernie --_000_489D13FBFA9B3E41812EA89F188F018E1AE0A6E0xmbrcdx04ciscoc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi:

 

Several points:

1.     &= nbsp; Publishing initial RFC 3315bis before modifications= .

2.     &= nbsp; Open issue tracker tickets for 3315/3633 bis issues= .

3.     &= nbsp; Next meeting? Wed Jan 15 @ 0800 US EST?<= /p>

 

1.       Publishing initial RFC 3315bis before modifications= :

 

I did some additional work on the RFC3315 bis docume= nt and plan to publish it as draft-dhcwg-dhc-rfc3315bis-00. You can see the= “final” versions at:

https://github.com/dhcwg/rfc3315bis/blob/master/rfc3= 315bis.txt

https://github.com/dhcwg/rfc3315bis/blob/master/rfc3= 315bis.xml

 

For now, I placed the original authors onto the docu= ment. As Ted and Ralph will be notified of this draft submission, I explain= ed to them what we are doing and will see if they have any comments/suggest= ions before I post it.

 

Note that we won’t publish the converted 3633 = because we don’t intend to have a ‘bis’ version of that; = instead that material will be merged into 3315. I’m not sure where th= e 3633 xml conversion stands; perhaps it is as complete as it needs to be?

 

2.       Open issue tracker tickets for 3315/3633 bis issues= :

 

A few tickets were opened at http://trac.tools.ietf.org/group/dhcpv6bis for errata and some other it= ems. I know I most go through my email to locate other issues I’ve ca= ptured over the years, and hopefully others will do the same. So, this is j= ust a friendly reminder to do that.

 

Note: Best to open one ticket per issue as this will= make it easier to track and mark complete. This is especially important fo= r any items that may  need some discussion before being ‘accepte= d’ (pre-existing approved errata, for example, are OK to list as one though even then having them separate means they don= ’t all need to be done ‘at once’).

 

3.       Next meeting?

 

How about we have another WebEx meeting Wednesday, J= an 15 @ 0800 US EST (same time as the last meeting) to determine next steps= . By then, we should have RFC3315bis and RFC3633bis in XML form and most is= sues tracked. And, that means to start work on updating the 3315bis document (based on tickets) and 3633 changes = and how to best do this.

 

Let me know if you are OK with the Wed Jan 15 meetin= g. Also, just in case that date doesn’t work well, let me know how We= d Jan 22nd works as an alternate. (Note that I will not be avail= able from 1/24-2/8.)

 

-     &= nbsp;    Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E1AE0A6E0xmbrcdx04ciscoc_-- From volz@cisco.com Tue Jan 7 08:34:47 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3D391ADFA0 for ; Tue, 7 Jan 2014 08:34:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.038 X-Spam-Level: X-Spam-Status: No, score=-15.038 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, RP_MATCHES_RCVD=-0.538, 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 wcwtk9LolRAJ for ; Tue, 7 Jan 2014 08:34:44 -0800 (PST) Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1762B1ADF72 for ; Tue, 7 Jan 2014 08:34:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20049; q=dns/txt; s=iport; t=1389112475; x=1390322075; h=from:to:subject:date:message-id:mime-version; bh=ehp29ZpZsDap4qqQV0H4JkfSYIW5++UG7S1zw168bCo=; b=QYY2wEWMljZJJ0sizNmgKVtp5EltSU4ItykEfy2EiQBPiqQEaGf/usvx YYZbBUbUQsz4Qj3Tw0O3hS5Kb0Xj4fyUeDS1iEFbW+Hci/R+3CgzqIWYF v1tZ/F6zYTLrnmw8rXurlgFolL8h9Q+wA0Os+IwhbFDsTIE9CqPwyZOjk Y=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArwFANErzFKtJV2Z/2dsb2JhbABZgkdEOFWxD4hWgRIWdIIlAQEBBC1eAQgRBAEBCxZAHQkBBBMIF4dlDZprqTUXjj8ULYMvgRMEmUeQZYMtgio X-IronPort-AV: E=Sophos;i="4.95,619,1384300800"; d="scan'208,217";a="295614043" Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-1.cisco.com with ESMTP; 07 Jan 2014 16:34:33 +0000 Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s07GYXBM004969 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 7 Jan 2014 16:34:33 GMT Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Tue, 7 Jan 2014 10:34:32 -0600 From: "Bernie Volz (volz)" To: "dhcpv6bis@ietf.org" Thread-Topic: Publish 3315bis, issue tracker, another meeting? Thread-Index: Ac8LMYUI34DxbQVfRYiRpDhWxSS0AQAlHgdA Date: Tue, 7 Jan 2014 16:34:31 +0000 Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE0BEB5@xmb-rcd-x04.cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [161.44.65.131] Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1AE0BEB5xmbrcdx04ciscoc_" MIME-Version: 1.0 Subject: Re: [Dhcpv6bis] Publish 3315bis, issue tracker, another meeting? X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jan 2014 16:34:48 -0000 --_000_489D13FBFA9B3E41812EA89F188F018E1AE0BEB5xmbrcdx04ciscoc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi: I should have checked my own calendar :(. Turns out I have a conflict Wed J= an 15 @ 0800. So, would probably not be able to attend (or only for portion= s). Let's see how it goes with responses (I haven't received any) regarding the= Wed Jan 15 or Wed Jan 22 dates and we'll determine whether to keep it the = 15th or move to 22nd. It will be difficult to always get everyone. - Bernie From: Bernie Volz (volz) Sent: Monday, January 06, 2014 5:50 PM To: dhcpv6bis@ietf.org Subject: Publish 3315bis, issue tracker, another meeting? Hi: Several points: 1. Publishing initial RFC 3315bis before modifications. 2. Open issue tracker tickets for 3315/3633 bis issues. 3. Next meeting? Wed Jan 15 @ 0800 US EST? 1. Publishing initial RFC 3315bis before modifications: I did some additional work on the RFC3315 bis document and plan to publish = it as draft-dhcwg-dhc-rfc3315bis-00. You can see the "final" versions at: https://github.com/dhcwg/rfc3315bis/blob/master/rfc3315bis.txt https://github.com/dhcwg/rfc3315bis/blob/master/rfc3315bis.xml For now, I placed the original authors onto the document. As Ted and Ralph = will be notified of this draft submission, I explained to them what we are = doing and will see if they have any comments/suggestions before I post it. Note that we won't publish the converted 3633 because we don't intend to ha= ve a 'bis' version of that; instead that material will be merged into 3315.= I'm not sure where the 3633 xml conversion stands; perhaps it is as comple= te as it needs to be? 2. Open issue tracker tickets for 3315/3633 bis issues: A few tickets were opened at http://trac.tools.ietf.org/group/dhcpv6bis for= errata and some other items. I know I most go through my email to locate o= ther issues I've captured over the years, and hopefully others will do the = same. So, this is just a friendly reminder to do that. Note: Best to open one ticket per issue as this will make it easier to trac= k and mark complete. This is especially important for any items that may n= eed some discussion before being 'accepted' (pre-existing approved errata, = for example, are OK to list as one though even then having them separate me= ans they don't all need to be done 'at once'). 3. Next meeting? How about we have another WebEx meeting Wednesday, Jan 15 @ 0800 US EST (sa= me time as the last meeting) to determine next steps. By then, we should ha= ve RFC3315bis and RFC3633bis in XML form and most issues tracked. And, that= means to start work on updating the 3315bis document (based on tickets) an= d 3633 changes and how to best do this. Let me know if you are OK with the Wed Jan 15 meeting. Also, just in case t= hat date doesn't work well, let me know how Wed Jan 22nd works as an altern= ate. (Note that I will not be available from 1/24-2/8.) - Bernie --_000_489D13FBFA9B3E41812EA89F188F018E1AE0BEB5xmbrcdx04ciscoc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi:<= /p>

 

I should have checked = my own calendar L. Turns out I have a conflict Wed Jan 15 @ 0800. So, = would probably not be able to attend (or only for portions).

 

Let’s see how it= goes with responses (I haven’t received any) regarding the Wed Jan 1= 5 or Wed Jan 22 dates and we’ll determine whether to keep it the 15th or move to 22nd. It will be difficult to always get everyone.

 

-&nb= sp;         Bernie

 

From: Bernie V= olz (volz)
Sent: Monday, January 06, 2014 5:50 PM
To: dhcpv6bis@ietf.org
Subject: Publish 3315bis, issue tracker, another meeting?=

 

Hi:

 

Several points:

1.     &= nbsp; Publishing initial RFC 3315bis before modifications= .

2.     &= nbsp; Open issue tracker tickets for 3315/3633 bis issues= .

3.     &= nbsp; Next meeting? Wed Jan 15 @ 0800 US EST?<= /p>

 

1.       Publishing initial RFC 3315bis before modifications= :

 

I did some additional work on the RFC3315 bis docume= nt and plan to publish it as draft-dhcwg-dhc-rfc3315bis-00. You can see the= “final” versions at:

https://github.com/dhcwg/rfc3315bis/blob/master/rfc3= 315bis.txt

https://github.com/dhcwg/rfc3315bis/blob/master/rfc3= 315bis.xml

 

For now, I placed the original authors onto the docu= ment. As Ted and Ralph will be notified of this draft submission, I explain= ed to them what we are doing and will see if they have any comments/suggest= ions before I post it.

 

Note that we won’t publish the converted 3633 = because we don’t intend to have a ‘bis’ version of that; = instead that material will be merged into 3315. I’m not sure where th= e 3633 xml conversion stands; perhaps it is as complete as it needs to be?

 

2.       Open issue tracker tickets for 3315/3633 bis issues= :

 

A few tickets were opened at http://trac.tools.ietf.org/group/dhcpv6bis for errata and some other it= ems. I know I most go through my email to locate other issues I’ve ca= ptured over the years, and hopefully others will do the same. So, this is j= ust a friendly reminder to do that.

 

Note: Best to open one ticket per issue as this will= make it easier to track and mark complete. This is especially important fo= r any items that may  need some discussion before being ‘accepte= d’ (pre-existing approved errata, for example, are OK to list as one though even then having them separate means they don= ’t all need to be done ‘at once’).

 

3.       Next meeting?

 

How about we have another WebEx meeting Wednesday, J= an 15 @ 0800 US EST (same time as the last meeting) to determine next steps= . By then, we should have RFC3315bis and RFC3633bis in XML form and most is= sues tracked. And, that means to start work on updating the 3315bis document (based on tickets) and 3633 changes = and how to best do this.

 

Let me know if you are OK with the Wed Jan 15 meetin= g. Also, just in case that date doesn’t work well, let me know how We= d Jan 22nd works as an alternate. (Note that I will not be avail= able from 1/24-2/8.)

 

-     &= nbsp;    Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E1AE0BEB5xmbrcdx04ciscoc_-- From msiodelski@gmail.com Wed Jan 8 00:22:23 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC32C1AE332 for ; Wed, 8 Jan 2014 00:22:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 yuqPYh7cOBtQ for ; Wed, 8 Jan 2014 00:22:21 -0800 (PST) Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) by ietfa.amsl.com (Postfix) with ESMTP id 5CE251AE336 for ; Wed, 8 Jan 2014 00:22:21 -0800 (PST) Received: by mail-lb0-f178.google.com with SMTP id c11so1035976lbj.23 for ; Wed, 08 Jan 2014 00:22:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=fXNj3Xq23YBY2waSqkzfSPe377bIHvLNK0vdoN3XOSE=; b=kUiclo23pf8KAEwpMvBuFIqp4Tk5K9BWxN3uGkWywHFR0JbeKKCMx/gBeo7lk3Cw+i 2/6Xn7RtIEtparksmigPkbE+dy0iW3xD8IGoUPE7RdLqwzKmET31coT7d/Ro8PLgJSAo wZUEE0rU2hy7m3UCo5Py8cIEl71mPa+vkQuafqiobnxTmbI8kLr3G3I+NSFi6m1fhitA //d4IwRovvJAqsvcbcx5/8KzD9R1/lpe4AvAPLsDOpCLQYtojwp+rOeq1ZWjpIZBdn4q 4JNtCPs/oFIIMBmBEEiFG7KzaXOt9fHmCvik2bBPdYFnXitfHlNMrsAq1jUoK/Bp8DwT 1VTQ== MIME-Version: 1.0 X-Received: by 10.152.10.10 with SMTP id e10mr5001461lab.56.1389169331533; Wed, 08 Jan 2014 00:22:11 -0800 (PST) Received: by 10.112.62.166 with HTTP; Wed, 8 Jan 2014 00:22:11 -0800 (PST) In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AE0BEB5@xmb-rcd-x04.cisco.com> References: <489D13FBFA9B3E41812EA89F188F018E1AE0BEB5@xmb-rcd-x04.cisco.com> Date: Wed, 8 Jan 2014 09:22:11 +0100 Message-ID: From: Marcin Siodelski To: "Bernie Volz (volz)" Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: "dhcpv6bis@ietf.org" Subject: Re: [Dhcpv6bis] Publish 3315bis, issue tracker, another meeting? X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jan 2014 08:22:23 -0000 Hi, Both Jan 15th and 22nd at 0800 EST work for me. Marcin On Tue, Jan 7, 2014 at 5:34 PM, Bernie Volz (volz) wrote: > Hi: > > > > I should have checked my own calendar L. Turns out I have a conflict Wed = Jan > 15 @ 0800. So, would probably not be able to attend (or only for portions= ). > > > > Let=92s see how it goes with responses (I haven=92t received any) regardi= ng the > Wed Jan 15 or Wed Jan 22 dates and we=92ll determine whether to keep it t= he > 15th or move to 22nd. It will be difficult to always get everyone. > > > > - Bernie > > > > From: Bernie Volz (volz) > Sent: Monday, January 06, 2014 5:50 PM > To: dhcpv6bis@ietf.org > Subject: Publish 3315bis, issue tracker, another meeting? > > > > Hi: > > > > Several points: > > 1. Publishing initial RFC 3315bis before modifications. > > 2. Open issue tracker tickets for 3315/3633 bis issues. > > 3. Next meeting? Wed Jan 15 @ 0800 US EST? > > > > 1. Publishing initial RFC 3315bis before modifications: > > > > I did some additional work on the RFC3315 bis document and plan to publis= h > it as draft-dhcwg-dhc-rfc3315bis-00. You can see the =93final=94 versions= at: > > https://github.com/dhcwg/rfc3315bis/blob/master/rfc3315bis.txt > > https://github.com/dhcwg/rfc3315bis/blob/master/rfc3315bis.xml > > > > For now, I placed the original authors onto the document. As Ted and Ralp= h > will be notified of this draft submission, I explained to them what we ar= e > doing and will see if they have any comments/suggestions before I post it= . > > > > Note that we won=92t publish the converted 3633 because we don=92t intend= to > have a =91bis=92 version of that; instead that material will be merged in= to > 3315. I=92m not sure where the 3633 xml conversion stands; perhaps it is = as > complete as it needs to be? > > > > 2. Open issue tracker tickets for 3315/3633 bis issues: > > > > A few tickets were opened at http://trac.tools.ietf.org/group/dhcpv6bis f= or > errata and some other items. I know I most go through my email to locate > other issues I=92ve captured over the years, and hopefully others will do= the > same. So, this is just a friendly reminder to do that. > > > > Note: Best to open one ticket per issue as this will make it easier to tr= ack > and mark complete. This is especially important for any items that may n= eed > some discussion before being =91accepted=92 (pre-existing approved errata= , for > example, are OK to list as one though even then having them separate mean= s > they don=92t all need to be done =91at once=92). > > > > 3. Next meeting? > > > > How about we have another WebEx meeting Wednesday, Jan 15 @ 0800 US EST > (same time as the last meeting) to determine next steps. By then, we shou= ld > have RFC3315bis and RFC3633bis in XML form and most issues tracked. And, > that means to start work on updating the 3315bis document (based on ticke= ts) > and 3633 changes and how to best do this. > > > > Let me know if you are OK with the Wed Jan 15 meeting. Also, just in case > that date doesn=92t work well, let me know how Wed Jan 22nd works as an > alternate. (Note that I will not be available from 1/24-2/8.) > > > > - Bernie > > > _______________________________________________ > Dhcpv6bis mailing list > Dhcpv6bis@ietf.org > https://www.ietf.org/mailman/listinfo/dhcpv6bis > From msiodelski@gmail.com Wed Jan 8 03:25:22 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EDD51AE281 for ; Wed, 8 Jan 2014 03:25:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 CoqpZBE7xbzW for ; Wed, 8 Jan 2014 03:25:20 -0800 (PST) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) by ietfa.amsl.com (Postfix) with ESMTP id 266881AE190 for ; Wed, 8 Jan 2014 03:25:19 -0800 (PST) Received: by mail-lb0-f179.google.com with SMTP id w7so1173424lbi.38 for ; Wed, 08 Jan 2014 03:25:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=PMRvA+jnZbTRz/pXaFD+d2szhW1vYmin4Eshw2ML7uM=; b=Zm8zZwF42PZEBRlkTjW7JN06L9w87xqfjYezHKYRW8XGVFPGZ9cLizlvVXwTonOIdE YKeLnXp+7Hsejkgq7LSGU/D113245Gg/EBYfkDfpEjhzP1zCyyGAQ+jq1vrr+Alnywx/ kRL/HTy+Zpxy6tQee2iN4hr5i9Z+7zqU6cjG7kweSsLlLlaOQ5oK6lL62Hh8Nuq3c2dy lJy33MtXracU2jR92N/MGlQi+87cWNooD6EepnUvr10oOgVGRIfQLZltuPEABhJfiHuk DK2lExwFq/tYlP+6i/inOU66akMR6d960xTemSlejjB5vnHAynXFZA4RjcYwv0PSurWX 6Eew== MIME-Version: 1.0 X-Received: by 10.112.181.232 with SMTP id dz8mr46484291lbc.8.1389180310309; Wed, 08 Jan 2014 03:25:10 -0800 (PST) Received: by 10.112.62.166 with HTTP; Wed, 8 Jan 2014 03:25:10 -0800 (PST) In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AE0A6E0@xmb-rcd-x04.cisco.com> References: <489D13FBFA9B3E41812EA89F188F018E1AE0A6E0@xmb-rcd-x04.cisco.com> Date: Wed, 8 Jan 2014 12:25:10 +0100 Message-ID: From: Marcin Siodelski To: "Bernie Volz (volz)" Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: "dhcpv6bis@ietf.org" Subject: Re: [Dhcpv6bis] Publish 3315bis, issue tracker, another meeting? X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jan 2014 11:25:22 -0000 Hi, > A few tickets were opened at http://trac.tools.ietf.org/group/dhcpv6bis f= or > errata and some other items. I know I most go through my email to locate > other issues I=92ve captured over the years, and hopefully others will do= the > same. So, this is just a friendly reminder to do that. > > > > Note: Best to open one ticket per issue as this will make it easier to tr= ack > and mark complete. This is especially important for any items that may n= eed > some discussion before being =91accepted=92 (pre-existing approved errata= , for > example, are OK to list as one though even then having them separate mean= s > they don=92t all need to be done =91at once=92). I concur that it is a good idea to track each errata item separately. I submitted individual tickets for each errata item for both RFC3315 and RFC3633. For now I left the tickets submitted by Sheng (#6, #7, #8, #9) which aggregate erratas. Perhaps they should be closed as duplicates of the new tickets? Marcin From volz@cisco.com Wed Jan 8 04:37:20 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F3861AE36A for ; Wed, 8 Jan 2014 04:37:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.039 X-Spam-Level: X-Spam-Status: No, score=-15.039 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, RP_MATCHES_RCVD=-0.538, 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 CCNECmMQP7VB for ; Wed, 8 Jan 2014 04:37:18 -0800 (PST) Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 7C35F1AE24D for ; Wed, 8 Jan 2014 04:37:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1715; q=dns/txt; s=iport; t=1389184629; x=1390394229; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=sL0/JNN6PhWhlT1nnjcDsDiooRF5mUn0/2sqjq3GU+k=; b=mnD9nuud3YREYhNx/D4Z15ddbx0N8CQZzZml/NyodyQ3VD3M6E1e8u3b fSWmWETCPy7b0rZ8KRG6OePM97xTGZffzKysK4SIh37jcGfVBRbmbqjsm ee3bSxXEYJHVsq6IeinsAGPhGapB/rSoZtcCEKbtdBlp69rxlEKClZgfN E=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgIFACZGzVKtJV2Z/2dsb2JhbABZgws4ukWBExZ0giUBAQEDAXkFCwIBCA4KLiERJQEBBA4Fh3ADCQgNv20NhHUXjHKBThIzB4MkgRMEliuBbIEwiyqFO4Mt X-IronPort-AV: E=Sophos;i="4.95,624,1384300800"; d="scan'208";a="295991755" Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-7.cisco.com with ESMTP; 08 Jan 2014 12:37:09 +0000 Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s08Cb9e1024611 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 8 Jan 2014 12:37:09 GMT Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0123.003; Wed, 8 Jan 2014 06:37:08 -0600 From: "Bernie Volz (volz)" To: Marcin Siodelski Thread-Topic: [Dhcpv6bis] Publish 3315bis, issue tracker, another meeting? Thread-Index: Ac8LMYUI34DxbQVfRYiRpDhWxSS0AQBZQ/gA//+vhbw= Date: Wed, 8 Jan 2014 12:37:07 +0000 Message-ID: <90EAA439-3CF8-47E7-ABC6-9683A8ACFFD1@cisco.com> References: <489D13FBFA9B3E41812EA89F188F018E1AE0A6E0@xmb-rcd-x04.cisco.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dhcpv6bis@ietf.org" Subject: Re: [Dhcpv6bis] Publish 3315bis, issue tracker, another meeting? X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jan 2014 12:37:20 -0000 Thanks ... Sadly I ended up ignoring my own suggestion at least in the case= of the 20+ issues Fred Templin had found. Some of these could duplicate ot= her reported issues. I probably should split these into separate tickets. I have one or two more emails that I have to review to see what the issue w= as and possibly add more tickets, but I think I added the bulk of the issue= s I had kept. I did notice a few minor issues while working on the conversi= on cleanup and need to add those if not already recorded. - Bernie (from iPad) > On Jan 8, 2014, at 6:25 AM, "Marcin Siodelski" wro= te: >=20 > Hi, >=20 >> A few tickets were opened at http://trac.tools.ietf.org/group/dhcpv6bis = for >> errata and some other items. I know I most go through my email to locate >> other issues I=92ve captured over the years, and hopefully others will d= o the >> same. So, this is just a friendly reminder to do that. >>=20 >>=20 >>=20 >> Note: Best to open one ticket per issue as this will make it easier to t= rack >> and mark complete. This is especially important for any items that may = need >> some discussion before being =91accepted=92 (pre-existing approved errat= a, for >> example, are OK to list as one though even then having them separate mea= ns >> they don=92t all need to be done =91at once=92). >=20 > I concur that it is a good idea to track each errata item separately. > I submitted individual tickets for each errata item for both RFC3315 > and RFC3633. For now I left the tickets submitted by Sheng (#6, #7, > #8, #9) which aggregate erratas. Perhaps they should be closed as > duplicates of the new tickets? >=20 >=20 > Marcin From jiangsheng@huawei.com Wed Jan 8 19:57:55 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CBAD1AE123 for ; Wed, 8 Jan 2014 19:57:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.739 X-Spam-Level: X-Spam-Status: No, score=-4.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] 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 x9cfBkH_TBLK for ; Wed, 8 Jan 2014 19:57:54 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 688B61AE027 for ; Wed, 8 Jan 2014 19:57:53 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCH71696; Thu, 09 Jan 2014 03:57:43 +0000 (GMT) Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 9 Jan 2014 03:57:17 +0000 Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 9 Jan 2014 03:57:42 +0000 Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.51]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Thu, 9 Jan 2014 11:57:39 +0800 From: Sheng Jiang To: "dhcpv6bis@ietf.org" Thread-Topic: [Dhcpv6bis] Publish 3315bis, issue tracker, another meeting? Thread-Index: Ac8LMYUI34DxbQVfRYiRpDhWxSS0AQAlHgdAABBrwoAAObeLUA== Date: Thu, 9 Jan 2014 03:57:38 +0000 Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923ADD27F2@nkgeml512-mbx.china.huawei.com> References: <489D13FBFA9B3E41812EA89F188F018E1AE0BEB5@xmb-rcd-x04.cisco.com> In-Reply-To: Accept-Language: en-GB, zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.111.98.145] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected Subject: Re: [Dhcpv6bis] Publish 3315bis, issue tracker, another meeting? X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jan 2014 03:57:55 -0000 PkJvdGggSmFuIDE1dGggYW5kIDIybmQgYXQgMDgwMCBFU1Qgd29yayBmb3IgbWUuDQoNCkFzIGxv bmcgYXMgaXQgaXMgdGhlIHNhbWUgdGltZSwgaXQgd29ya3MgZm9yIG1lLCBJIGRvbid0IHJlYWxs eSBtaW5kIHdoaWNoIGRheSBpdCBpcy4gU2luY2UgaXQgaXMgYXQgbmlnaHRzIGZvciBtZSwgSSBk b24ndCBoYXZlIGFueSBjb25mbGljdGlvbnMuIDopIA0KDQpDaGVlcnMsDQoNClNoZW5nDQoNCg0K Pk1hcmNpbg0KPg0KPk9uIFR1ZSwgSmFuIDcsIDIwMTQgYXQgNTozNCBQTSwgQmVybmllIFZvbHog KHZvbHopIDx2b2x6QGNpc2NvLmNvbT4gd3JvdGU6DQo+PiBIaToNCj4+DQo+Pg0KPj4NCj4+IEkg c2hvdWxkIGhhdmUgY2hlY2tlZCBteSBvd24gY2FsZW5kYXIgTC4gVHVybnMgb3V0IEkgaGF2ZSBh IGNvbmZsaWN0IFdlZA0KPkphbg0KPj4gMTUgQCAwODAwLiBTbywgd291bGQgcHJvYmFibHkgbm90 IGJlIGFibGUgdG8gYXR0ZW5kIChvciBvbmx5IGZvciBwb3J0aW9ucykuDQo+Pg0KPj4NCj4+DQo+ PiBMZXTigJlzIHNlZSBob3cgaXQgZ29lcyB3aXRoIHJlc3BvbnNlcyAoSSBoYXZlbuKAmXQgcmVj ZWl2ZWQgYW55KSByZWdhcmRpbmcgdGhlDQo+PiBXZWQgSmFuIDE1IG9yIFdlZCBKYW4gMjIgZGF0 ZXMgYW5kIHdl4oCZbGwgZGV0ZXJtaW5lIHdoZXRoZXIgdG8ga2VlcCBpdCB0aGUNCj4+IDE1dGgg b3IgbW92ZSB0byAyMm5kLiBJdCB3aWxsIGJlIGRpZmZpY3VsdCB0byBhbHdheXMgZ2V0IGV2ZXJ5 b25lLg0KPj4NCj4+DQo+Pg0KPj4gLSAgICAgICAgICBCZXJuaWUNCj4+DQo+Pg0KPj4NCj4+IEZy b206IEJlcm5pZSBWb2x6ICh2b2x6KQ0KPj4gU2VudDogTW9uZGF5LCBKYW51YXJ5IDA2LCAyMDE0 IDU6NTAgUE0NCj4+IFRvOiBkaGNwdjZiaXNAaWV0Zi5vcmcNCj4+IFN1YmplY3Q6IFB1Ymxpc2gg MzMxNWJpcywgaXNzdWUgdHJhY2tlciwgYW5vdGhlciBtZWV0aW5nPw0KPj4NCj4+DQo+Pg0KPj4g SGk6DQo+Pg0KPj4NCj4+DQo+PiBTZXZlcmFsIHBvaW50czoNCj4+DQo+PiAxLiAgICAgICBQdWJs aXNoaW5nIGluaXRpYWwgUkZDIDMzMTViaXMgYmVmb3JlIG1vZGlmaWNhdGlvbnMuDQo+Pg0KPj4g Mi4gICAgICAgT3BlbiBpc3N1ZSB0cmFja2VyIHRpY2tldHMgZm9yIDMzMTUvMzYzMyBiaXMgaXNz dWVzLg0KPj4NCj4+IDMuICAgICAgIE5leHQgbWVldGluZz8gV2VkIEphbiAxNSBAIDA4MDAgVVMg RVNUPw0KPj4NCj4+DQo+Pg0KPj4gMS4gICAgICAgUHVibGlzaGluZyBpbml0aWFsIFJGQyAzMzE1 YmlzIGJlZm9yZSBtb2RpZmljYXRpb25zOg0KPj4NCj4+DQo+Pg0KPj4gSSBkaWQgc29tZSBhZGRp dGlvbmFsIHdvcmsgb24gdGhlIFJGQzMzMTUgYmlzIGRvY3VtZW50IGFuZCBwbGFuIHRvIHB1Ymxp c2gNCj4+IGl0IGFzIGRyYWZ0LWRoY3dnLWRoYy1yZmMzMzE1YmlzLTAwLiBZb3UgY2FuIHNlZSB0 aGUg4oCcZmluYWzigJ0gdmVyc2lvbnMgYXQ6DQo+Pg0KPj4gaHR0cHM6Ly9naXRodWIuY29tL2Ro Y3dnL3JmYzMzMTViaXMvYmxvYi9tYXN0ZXIvcmZjMzMxNWJpcy50eHQNCj4+DQo+PiBodHRwczov L2dpdGh1Yi5jb20vZGhjd2cvcmZjMzMxNWJpcy9ibG9iL21hc3Rlci9yZmMzMzE1YmlzLnhtbA0K Pj4NCj4+DQo+Pg0KPj4gRm9yIG5vdywgSSBwbGFjZWQgdGhlIG9yaWdpbmFsIGF1dGhvcnMgb250 byB0aGUgZG9jdW1lbnQuIEFzIFRlZCBhbmQgUmFscGgNCj4+IHdpbGwgYmUgbm90aWZpZWQgb2Yg dGhpcyBkcmFmdCBzdWJtaXNzaW9uLCBJIGV4cGxhaW5lZCB0byB0aGVtIHdoYXQgd2UgYXJlDQo+ PiBkb2luZyBhbmQgd2lsbCBzZWUgaWYgdGhleSBoYXZlIGFueSBjb21tZW50cy9zdWdnZXN0aW9u cyBiZWZvcmUgSSBwb3N0IGl0Lg0KPj4NCj4+DQo+Pg0KPj4gTm90ZSB0aGF0IHdlIHdvbuKAmXQg cHVibGlzaCB0aGUgY29udmVydGVkIDM2MzMgYmVjYXVzZSB3ZSBkb27igJl0IGludGVuZA0KPnRv DQo+PiBoYXZlIGEg4oCYYmlz4oCZIHZlcnNpb24gb2YgdGhhdDsgaW5zdGVhZCB0aGF0IG1hdGVy aWFsIHdpbGwgYmUgbWVyZ2VkIGludG8NCj4+IDMzMTUuIEnigJltIG5vdCBzdXJlIHdoZXJlIHRo ZSAzNjMzIHhtbCBjb252ZXJzaW9uIHN0YW5kczsgcGVyaGFwcyBpdCBpcyBhcw0KPj4gY29tcGxl dGUgYXMgaXQgbmVlZHMgdG8gYmU/DQo+Pg0KPj4NCj4+DQo+PiAyLiAgICAgICBPcGVuIGlzc3Vl IHRyYWNrZXIgdGlja2V0cyBmb3IgMzMxNS8zNjMzIGJpcyBpc3N1ZXM6DQo+Pg0KPj4NCj4+DQo+ PiBBIGZldyB0aWNrZXRzIHdlcmUgb3BlbmVkIGF0IGh0dHA6Ly90cmFjLnRvb2xzLmlldGYub3Jn L2dyb3VwL2RoY3B2NmJpcyBmb3INCj4+IGVycmF0YSBhbmQgc29tZSBvdGhlciBpdGVtcy4gSSBr bm93IEkgbW9zdCBnbyB0aHJvdWdoIG15IGVtYWlsIHRvIGxvY2F0ZQ0KPj4gb3RoZXIgaXNzdWVz IEnigJl2ZSBjYXB0dXJlZCBvdmVyIHRoZSB5ZWFycywgYW5kIGhvcGVmdWxseSBvdGhlcnMgd2ls bCBkbyB0aGUNCj4+IHNhbWUuIFNvLCB0aGlzIGlzIGp1c3QgYSBmcmllbmRseSByZW1pbmRlciB0 byBkbyB0aGF0Lg0KPj4NCj4+DQo+Pg0KPj4gTm90ZTogQmVzdCB0byBvcGVuIG9uZSB0aWNrZXQg cGVyIGlzc3VlIGFzIHRoaXMgd2lsbCBtYWtlIGl0IGVhc2llciB0byB0cmFjaw0KPj4gYW5kIG1h cmsgY29tcGxldGUuIFRoaXMgaXMgZXNwZWNpYWxseSBpbXBvcnRhbnQgZm9yIGFueSBpdGVtcyB0 aGF0IG1heQ0KPm5lZWQNCj4+IHNvbWUgZGlzY3Vzc2lvbiBiZWZvcmUgYmVpbmcg4oCYYWNjZXB0 ZWTigJkgKHByZS1leGlzdGluZyBhcHByb3ZlZCBlcnJhdGEsIGZvcg0KPj4gZXhhbXBsZSwgYXJl IE9LIHRvIGxpc3QgYXMgb25lIHRob3VnaCBldmVuIHRoZW4gaGF2aW5nIHRoZW0gc2VwYXJhdGUN Cj5tZWFucw0KPj4gdGhleSBkb27igJl0IGFsbCBuZWVkIHRvIGJlIGRvbmUg4oCYYXQgb25jZeKA mSkuDQo+Pg0KPj4NCj4+DQo+PiAzLiAgICAgICBOZXh0IG1lZXRpbmc/DQo+Pg0KPj4NCj4+DQo+ PiBIb3cgYWJvdXQgd2UgaGF2ZSBhbm90aGVyIFdlYkV4IG1lZXRpbmcgV2VkbmVzZGF5LCBKYW4g MTUgQCAwODAwIFVTDQo+RVNUDQo+PiAoc2FtZSB0aW1lIGFzIHRoZSBsYXN0IG1lZXRpbmcpIHRv IGRldGVybWluZSBuZXh0IHN0ZXBzLiBCeSB0aGVuLCB3ZSBzaG91bGQNCj4+IGhhdmUgUkZDMzMx NWJpcyBhbmQgUkZDMzYzM2JpcyBpbiBYTUwgZm9ybSBhbmQgbW9zdCBpc3N1ZXMgdHJhY2tlZC4g QW5kLA0KPj4gdGhhdCBtZWFucyB0byBzdGFydCB3b3JrIG9uIHVwZGF0aW5nIHRoZSAzMzE1Ymlz IGRvY3VtZW50IChiYXNlZCBvbg0KPnRpY2tldHMpDQo+PiBhbmQgMzYzMyBjaGFuZ2VzIGFuZCBo b3cgdG8gYmVzdCBkbyB0aGlzLg0KPj4NCj4+DQo+Pg0KPj4gTGV0IG1lIGtub3cgaWYgeW91IGFy ZSBPSyB3aXRoIHRoZSBXZWQgSmFuIDE1IG1lZXRpbmcuIEFsc28sIGp1c3QgaW4gY2FzZQ0KPj4g dGhhdCBkYXRlIGRvZXNu4oCZdCB3b3JrIHdlbGwsIGxldCBtZSBrbm93IGhvdyBXZWQgSmFuIDIy bmQgd29ya3MgYXMgYW4NCj4+IGFsdGVybmF0ZS4gKE5vdGUgdGhhdCBJIHdpbGwgbm90IGJlIGF2 YWlsYWJsZSBmcm9tIDEvMjQtMi84LikNCj4+DQo+Pg0KPj4NCj4+IC0gICAgICAgICAgQmVybmll DQo+Pg0KPj4NCj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fDQo+PiBEaGNwdjZiaXMgbWFpbGluZyBsaXN0DQo+PiBEaGNwdjZiaXNAaWV0Zi5vcmcNCj4+ IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZGhjcHY2YmlzDQo+Pg0KPl9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+RGhjcHY2Ymlz IG1haWxpbmcgbGlzdA0KPkRoY3B2NmJpc0BpZXRmLm9yZw0KPmh0dHBzOi8vd3d3LmlldGYub3Jn L21haWxtYW4vbGlzdGluZm8vZGhjcHY2YmlzDQo= From volz@cisco.com Mon Jan 13 10:07:00 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F65B1ADF90 for ; Mon, 13 Jan 2014 10:07:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.038 X-Spam-Level: X-Spam-Status: No, score=-15.038 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, RP_MATCHES_RCVD=-0.538, 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 utcOsbop6b1d for ; Mon, 13 Jan 2014 10:06:57 -0800 (PST) Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 6C5651A1F5D for ; Mon, 13 Jan 2014 10:06:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12697; q=dns/txt; s=iport; t=1389636406; x=1390846006; h=from:to:subject:date:message-id:mime-version; bh=wbXpEZQ0iVsmlAdFQPYBOPBeyOUQBzU95i8D/Bkh/fs=; b=GQjOiPcNCT0fNfCBU3Zo7CI/nj0o1vFpsWLiUsT0wt6O9jIt+lMEP7Bs WOh/Nbx1g0yph9g+TxCM+J1ifSM1bAf55AUNOWKV+wLsgRl6NTgMTHm2+ QbxODDJUcdpKQHPH9zz/AHpDiIhzYyHIDfCXPXwQoj/jKFthBAJ3SJSP1 A=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ak0FAOop1FKtJV2Z/2dsb2JhbABAFwOCR0Q4VoJ+tnMYfxZ0gicBBCMKKBElASoKBBICBDAkAgEBAxuHfA02mk6PEZpaF45DExYLDBwHglc1gRMEhVeDNJA8kGWCW1KCKg X-IronPort-AV: E=Sophos;i="4.95,654,1384300800"; d="scan'208,217";a="296987367" Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 13 Jan 2014 18:06:46 +0000 Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0DI6kcR026570 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 13 Jan 2014 18:06:46 GMT Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0123.003; Mon, 13 Jan 2014 12:06:45 -0600 From: "Bernie Volz (volz)" To: "dhcpv6bis@ietf.org" Thread-Topic: DHCPv6bis Team Meeting - Next Steps Thread-Index: Ac8QieqpXhkOFfVxRXyHNgY4uAgDuAAAEyuQ Date: Mon, 13 Jan 2014 18:06:45 +0000 Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE1B27C@xmb-rcd-x04.cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.86.240.189] Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1AE1B27Cxmbrcdx04ciscoc_" MIME-Version: 1.0 Subject: [Dhcpv6bis] DHCPv6bis Team Meeting - Next Steps X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 18:07:00 -0000 --_000_489D13FBFA9B3E41812EA89F188F018E1AE1B27Cxmbrcdx04ciscoc_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Discuss how to proceed with applying issues and merging 3633 (and whatever = else). Please be sure to add items to the issue tracker! Agenda to follow (if you have any items, please let Tomek and I know). ******* DO NOT DELETE OR CHANGE ANY OF THE TEXT BELOW THIS LINE ******* ----------------------------------------------------------------------- JOIN USING WebEx Go To: https://cisco.webex.com/cisco/j.php?J=3D204539449&PW=3DNNzJlYzE3MTk3 Meeting Password ----- 3315 Meeting Number ----- 204 539 449 ---------------------------------------------------------------- ALERT - PLEASE READ: DO NOT DIAL THE TOLL FREE NUMBERS FROM WITHIN THE (408= ) OR (919) AREA CODES ---------------------------------------------------------------- Please dial the local access number for your area from the list below: - San Jose/Milpitas (408) area: 525-6800 - RTP (919) area: 392-3330 Dialing the WebEx toll free numbers from within 408 or 919 area codes is no= t enabled (non-Cisco phones). " If you dial the toll-free numbers within t= he 408 or 919 area codes you will be instructed to hang up and dial the loc= al access number." Please use the call-back option whenever possible and ot= herwise dial local numbers only. The affected toll free numbers are: (866)= 432-9903 for the San Jose/Milpitas area and (866) 349-3520 for the RTP are= a. ------------------------------------------------------- To join the teleconference only ------------------------------------------------------- 1. Dial into Cisco WebEx (view all Global Access Numbers at http://cisco.com/en/US/about/doing_business/conferencing/index.html 2. Follow the prompts to enter the Meeting Number (listed above) or Access = Code followed by the # sign. San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330 US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117 India: +91.80.4350.1111 Germany: +49.619.6773.9002 Japan: +81.3.5763.9394 China: +86.10.8515.5666 IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a= nd any documents and other materials exchanged or viewed during the session= to be recorded. By joining this session, you automatically consent to such= recordings. If you do not consent to the recording, discuss your concerns = with the meeting host prior to the start of the recording or do not join th= e session. Please note that any such recordings may be subject to discovery= in the event of litigation. http://www.webex.com --_000_489D13FBFA9B3E41812EA89F188F018E1AE1B27Cxmbrcdx04ciscoc_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Discuss how to proceed with applying issues and merging 3633 (and what= ever else). Please be sure to add items to the issue tracker!
 
Agenda to follow (if you have any items, please let Tomek and I know).=
 
 
 
******* DO NOT DELETE OR CHANGE ANY= OF THE TEXT BELOW THIS LINE *******
 
----------------------------------------------------------------------= -
JOIN USING WebEx
 
Go To:
 
Meeting Password ----- 3315
Meeting Number ----- 204 539 449
 
----------------------------------------------------------------
ALERT – PLEASE READ: DO NOT DIAL THE TOLL FREE NUMBERS FROM WITH= IN THE (408) OR (919) AREA CODES
----------------------------------------------------------------
Please dial the local access number for your area from the list below:=
-  San Jose/Milpitas (408) area:  525-6800
-  RTP (919) area:  392-3330
 
Dialing the WebEx toll free numbers from within 408 or 919 area codes = is not enabled (non-Cisco phones).  “ If you dial the toll-free = numbers within the 408 or 919 area codes you will be instructed to hang up = and dial the local access number.” Please use the call-back option whenever possible and otherwise dial local numbers onl= y.  The affected toll free numbers are: (866) 432-9903 for the San Jos= e/Milpitas area and (866) 349-3520 for the RTP area.
 
-------------------------------------------------------
To join the teleconference only
-------------------------------------------------------
1. Dial into Cisco WebEx (view all Global Access Numbers at
2. Follow the prompts to enter the Meeting Number (listed above) or Ac= cess Code followed by the # sign.
 
San Jose, CA: +1.408.525.6800  RTP: +1.919.392.3330
 
US/Canada: +1.866.432.9903  United Kingdom: +44.20.8824.0= 117
 
India: +91.80.4350.1111  Germany: +49.619.6773.9002
 
Japan: +81.3.5763.9394  China: +86.10.8515.5666
 
IMPORTANT NOTICE: This WebEx service includes a feature that allows au= dio and any documents and other materials exchanged or viewed during the se= ssion to be recorded. By joining this session, you automatically consent to= such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior= to the start of the recording or do not join the session. Please note that= any such recordings may be subject to discovery in the event of litigation= .
 
 
 
 --_000_489D13FBFA9B3E41812EA89F188F018E1AE1B27Cxmbrcdx04ciscoc_ Content-Type: text/calendar; charset="utf-8"; method=REQUEST Content-Transfer-Encoding: base64 QkVHSU46VkNBTEVOREFSDQpNRVRIT0Q6UkVRVUVTVA0KUFJPRElEOk1pY3Jvc29mdCBFeGNoYW5n ZSBTZXJ2ZXIgMjAxMA0KVkVSU0lPTjoyLjANCkJFR0lOOlZUSU1FWk9ORQ0KVFpJRDpFYXN0ZXJu IFN0YW5kYXJkIFRpbWUNCkJFR0lOOlNUQU5EQVJEDQpEVFNUQVJUOjE2MDEwMTAxVDAyMDAwMA0K VFpPRkZTRVRGUk9NOi0wNDAwDQpUWk9GRlNFVFRPOi0wNTAwDQpSUlVMRTpGUkVRPVlFQVJMWTtJ TlRFUlZBTD0xO0JZREFZPTFTVTtCWU1PTlRIPTExDQpFTkQ6U1RBTkRBUkQNCkJFR0lOOkRBWUxJ R0hUDQpEVFNUQVJUOjE2MDEwMTAxVDAyMDAwMA0KVFpPRkZTRVRGUk9NOi0wNTAwDQpUWk9GRlNF VFRPOi0wNDAwDQpSUlVMRTpGUkVRPVlFQVJMWTtJTlRFUlZBTD0xO0JZREFZPTJTVTtCWU1PTlRI PTMNCkVORDpEQVlMSUdIVA0KRU5EOlZUSU1FWk9ORQ0KQkVHSU46VkVWRU5UDQpPUkdBTklaRVI7 Q049QmVybmllIFZvbHogKHZvbHopOk1BSUxUTzp2b2x6QGNpc2NvLmNvbQ0KQVRURU5ERUU7Uk9M RT1SRVEtUEFSVElDSVBBTlQ7UEFSVFNUQVQ9TkVFRFMtQUNUSU9OO1JTVlA9VFJVRTtDTj1kaGNw djZiaXNADQogaWV0Zi5vcmc6TUFJTFRPOmRoY3B2NmJpc0BpZXRmLm9yZw0KREVTQ1JJUFRJT047 TEFOR1VBR0U9ZW4tVVM6RGlzY3VzcyBob3cgdG8gcHJvY2VlZCB3aXRoIGFwcGx5aW5nIGlzc3Vl cyBhbmQgDQogbWVyZ2luZyAzNjMzIChhbmQgd2hhdGV2ZXIgZWxzZSkuIFBsZWFzZSBiZSBzdXJl IHRvIGFkZCBpdGVtcyB0byB0aGUgaXNzdWUNCiAgdHJhY2tlciFcblxuQWdlbmRhIHRvIGZvbGxv dyAoaWYgeW91IGhhdmUgYW55IGl0ZW1zXCwgcGxlYXNlIGxldCBUb21layBhbg0KIGQgSSBrbm93 KS5cblxuXG5cbioqKioqKiogRE8gTk9UIERFTEVURSBPUiBDSEFOR0UgQU5ZIE9GIFRIRSBURVhU IEJFTE9XIFRIDQogSVMgTElORSAqKioqKioqXG5cbi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCiAtLS0tLS0tLS0tLS0tLS0tXG5KT0lOIFVT SU5HIFdlYkV4XG5cbkdvIFRvOlxuaHR0cHM6Ly9jaXNjby53ZWJleC5jb20vY2lzYw0KIG8vai5w aHA/Sj0yMDQ1Mzk0NDkmUFc9Tk56SmxZekUzTVRrM1xuXG5NZWV0aW5nIFBhc3N3b3JkIC0tLS0t IDMzMTVcbk1lZXRpDQogbmcgTnVtYmVyIC0tLS0tIDIwNCA1MzkgNDQ5XG5cbi0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCiAtLS0tLS0tLS0tLS0tLS0tLS0tLS1c bkFMRVJUIOKAkyBQTEVBU0UgUkVBRDogRE8gTk9UIERJQUwgVEhFIFRPTEwgRlJFRSBOVQ0KIE1C RVJTIEZST00gV0lUSElOIFRIRSAoNDA4KSBPUiAoOTE5KSBBUkVBIENPREVTXG4tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tDQogLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t XG5QbGVhc2UgZGlhbCB0aGUgbG9jYWwgYWNjZXNzIG51bWINCiBlciBmb3IgeW91ciBhcmVhIGZy b20gdGhlIGxpc3QgYmVsb3c6XG4tICBTYW4gSm9zZS9NaWxwaXRhcyAoNDA4KSBhcmVhOiAgNQ0K IDI1LTY4MDBcbi0gIFJUUCAoOTE5KSBhcmVhOiAgMzkyLTMzMzBcblxuRGlhbGluZyB0aGUgV2Vi RXggdG9sbCBmcmVlIG51bWJlDQogcnMgZnJvbSB3aXRoaW4gNDA4IG9yIDkxOSBhcmVhIGNvZGVz IGlzIG5vdCBlbmFibGVkIChub24tQ2lzY28gcGhvbmVzKS4gIA0KIOKAnCBJZiB5b3UgZGlhbCB0 aGUgdG9sbC1mcmVlIG51bWJlcnMgd2l0aGluIHRoZSA0MDggb3IgOTE5IGFyZWEgY29kZXMgeW91 DQogIHdpbGwgYmUgaW5zdHJ1Y3RlZCB0byBoYW5nIHVwIGFuZCBkaWFsIHRoZSBsb2NhbCBhY2Nl c3MgbnVtYmVyLuKAnSBQbGVhc2UNCiAgdXNlIHRoZSBjYWxsLWJhY2sgb3B0aW9uIHdoZW5ldmVy IHBvc3NpYmxlIGFuZCBvdGhlcndpc2UgZGlhbCBsb2NhbCBudW1iZQ0KIHJzIG9ubHkuICBUaGUg YWZmZWN0ZWQgdG9sbCBmcmVlIG51bWJlcnMgYXJlOiAoODY2KSA0MzItOTkwMyBmb3IgdGhlIFNh biBKDQogb3NlL01pbHBpdGFzIGFyZWEgYW5kICg4NjYpIDM0OS0zNTIwIGZvciB0aGUgUlRQIGFy ZWEuXG5cbi0tLS0tLS0tLS0tLS0tLS0NCiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS1cblRvIGpvaW4gdGhlIHRlbGVjb25mZXJlbmNlIG9ubHlcbg0KIC0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS1cbjEuIERpYWwgaW50 byBDaXNjDQogbyBXZWJFeCAodmlldyBhbGwgR2xvYmFsIEFjY2VzcyBOdW1iZXJzIGF0XG5odHRw Oi8vY2lzY28uY29tL2VuL1VTL2Fib3V0L2QNCiBvaW5nX2J1c2luZXNzL2NvbmZlcmVuY2luZy9p bmRleC5odG1sXG4yLiBGb2xsb3cgdGhlIHByb21wdHMgdG8gZW50ZXIgdGhlIA0KIE1lZXRpbmcg TnVtYmVyIChsaXN0ZWQgYWJvdmUpIG9yIEFjY2VzcyBDb2RlIGZvbGxvd2VkIGJ5IHRoZSAjIHNp Z24uXG5cblNhDQogbiBKb3NlXCwgQ0E6ICsxLjQwOC41MjUuNjgwMCAgUlRQOiArMS45MTkuMzky LjMzMzBcblxuVVMvQ2FuYWRhOiArMS44NjYuNDMNCiAyLjk5MDMgIFVuaXRlZCBLaW5nZG9tOiAr NDQuMjAuODgyNC4wMTE3XG5cbkluZGlhOiArOTEuODAuNDM1MC4xMTExICBHZXJtYQ0KIG55OiAr NDkuNjE5LjY3NzMuOTAwMlxuXG5KYXBhbjogKzgxLjMuNTc2My45Mzk0ICBDaGluYTogKzg2LjEw Ljg1MTUuNTY2NlxuDQogXG5JTVBPUlRBTlQgTk9USUNFOiBUaGlzIFdlYkV4IHNlcnZpY2UgaW5j bHVkZXMgYSBmZWF0dXJlIHRoYXQgYWxsb3dzIGF1ZGkNCiBvIGFuZCBhbnkgZG9jdW1lbnRzIGFu ZCBvdGhlciBtYXRlcmlhbHMgZXhjaGFuZ2VkIG9yIHZpZXdlZCBkdXJpbmcgdGhlIHNlcw0KIHNp b24gdG8gYmUgcmVjb3JkZWQuIEJ5IGpvaW5pbmcgdGhpcyBzZXNzaW9uXCwgeW91IGF1dG9tYXRp Y2FsbHkgY29uc2VudCB0DQogbyBzdWNoIHJlY29yZGluZ3MuIElmIHlvdSBkbyBub3QgY29uc2Vu dCB0byB0aGUgcmVjb3JkaW5nXCwgZGlzY3VzcyB5b3VyIGMNCiBvbmNlcm5zIHdpdGggdGhlIG1l ZXRpbmcgaG9zdCBwcmlvciB0byB0aGUgc3RhcnQgb2YgdGhlIHJlY29yZGluZyBvciBkbyBubw0K IHQgam9pbiB0aGUgc2Vzc2lvbi4gUGxlYXNlIG5vdGUgdGhhdCBhbnkgc3VjaCByZWNvcmRpbmdz IG1heSBiZSBzdWJqZWN0IHRvDQogIGRpc2NvdmVyeSBpbiB0aGUgZXZlbnQgb2YgbGl0aWdhdGlv bi5cblxuaHR0cDovL3d3dy53ZWJleC5jb21cblxuXG4NClNVTU1BUlk7TEFOR1VBR0U9ZW4tVVM6 REhDUHY2YmlzIFRlYW0gTWVldGluZyAtIE5leHQgU3RlcHMNCkRUU1RBUlQ7VFpJRD1FYXN0ZXJu IFN0YW5kYXJkIFRpbWU6MjAxNDAxMjJUMDgwMDAwDQpEVEVORDtUWklEPUVhc3Rlcm4gU3RhbmRh cmQgVGltZToyMDE0MDEyMlQwOTAwMDANClVJRDowNDAwMDAwMDgyMDBFMDAwNzRDNUI3MTAxQTgy RTAwODAwMDAwMDAwQTA1MzFGNEM2MDEwQ0YwMTAwMDAwMDAwMDAwMDAwMA0KIDAxMDAwMDAwMDhB NTZERjFGRDk0NzQzNDc5RDMxRjFCMjUxMzlGQTIxDQpDTEFTUzpQVUJMSUMNClBSSU9SSVRZOjUN CkRUU1RBTVA6MjAxNDAxMTNUMTgwNjQzWg0KVFJBTlNQOk9QQVFVRQ0KU1RBVFVTOkNPTkZJUk1F RA0KU0VRVUVOQ0U6MA0KTE9DQVRJT047TEFOR1VBR0U9ZW4tVVM6V2ViRXgNClgtTUlDUk9TT0ZU LUNETy1BUFBULVNFUVVFTkNFOjANClgtTUlDUk9TT0ZULUNETy1PV05FUkFQUFRJRDotMTIzNjQ2 MTYwMg0KWC1NSUNST1NPRlQtQ0RPLUJVU1lTVEFUVVM6VEVOVEFUSVZFDQpYLU1JQ1JPU09GVC1D RE8tSU5URU5ERURTVEFUVVM6QlVTWQ0KWC1NSUNST1NPRlQtQ0RPLUFMTERBWUVWRU5UOkZBTFNF DQpYLU1JQ1JPU09GVC1DRE8tSU1QT1JUQU5DRToxDQpYLU1JQ1JPU09GVC1DRE8tSU5TVFRZUEU6 MA0KWC1NSUNST1NPRlQtRElTQUxMT1ctQ09VTlRFUjpGQUxTRQ0KQkVHSU46VkFMQVJNDQpBQ1RJ T046RElTUExBWQ0KREVTQ1JJUFRJT046UkVNSU5ERVINClRSSUdHRVI7UkVMQVRFRD1TVEFSVDot UFQxNU0NCkVORDpWQUxBUk0NCkVORDpWRVZFTlQNCkVORDpWQ0FMRU5EQVINCg== --_000_489D13FBFA9B3E41812EA89F188F018E1AE1B27Cxmbrcdx04ciscoc_-- From mcr@sandelman.ca Tue Jan 14 11:46:01 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE6D81AE23F for ; Tue, 14 Jan 2014 11:46:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.019 X-Spam-Level: * X-Spam-Status: No, score=1.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no 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 o6xWXNe5tEdA for ; Tue, 14 Jan 2014 11:46:00 -0800 (PST) Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 880D11AE241 for ; Tue, 14 Jan 2014 11:45:59 -0800 (PST) Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id EBF0F2002C for ; Tue, 14 Jan 2014 16:01:28 -0500 (EST) Received: by sandelman.ca (Postfix, from userid 179) id 3768264647; Tue, 14 Jan 2014 14:45:46 -0500 (EST) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 1BCBA63AAE for ; Tue, 14 Jan 2014 14:45:46 -0500 (EST) From: Michael Richardson To: "dhcpv6bis\@ietf.org" In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AE1B27C@xmb-rcd-x04.cisco.com> References: <489D13FBFA9B3E41812EA89F188F018E1AE1B27C@xmb-rcd-x04.cisco.com> X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Sender: mcr@sandelman.ca Subject: Re: [Dhcpv6bis] DHCPv6bis Team Meeting - Next Steps X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jan 2014 19:46:01 -0000 --=-=-= The date for this call seems to be missing. Starting date: Wednesday, January 22, 2014 Starting time: 2:00 pm, Europe Time (Paris, GMT+01:00) Is what the webex says.... so that's 8am EST. I'm repeating this for others. -- Michael Richardson , Sandelman Software Works --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQCVAwUBUtWT54qHRg3pndX9AQJlewP/SWw+lDH2KJDlF93FRwCEFEb4JShPhMjd Qeyu/X24RMNLkXIB0EQrkPAWaxxtNAfmV8p4rtX4cQVUa5yZDIlmJiGRD94tQx3Q h3uaaDwk/EB9aPSo2RxCvxiPdHuls+TVwLRijo/kqwWENM7d3swfn5f5QvI6AQtc k4UGSVhA/4U= =emjl -----END PGP SIGNATURE----- --=-=-=-- From volz@cisco.com Tue Jan 14 14:44:40 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 175341AE25B for ; Tue, 14 Jan 2014 14:44:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.038 X-Spam-Level: X-Spam-Status: No, score=-10.038 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, RP_MATCHES_RCVD=-0.538, 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 dKkFC8kYuHvg for ; Tue, 14 Jan 2014 14:44:37 -0800 (PST) Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id 697911AE22E for ; Tue, 14 Jan 2014 14:44:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9203; q=dns/txt; s=iport; t=1389739465; x=1390949065; h=from:to:subject:date:message-id:mime-version; bh=c3VpCgD/JcRTuCU2ha03fsSQY96M5rBeWEif8/8ko+o=; b=bIHi//+WiW0jpePSk5Ia7h8ath4fSE1qhvFTnmCdMIJVBFK2s/upboKO FmSQ0d1FtyKgwgNe6+dzj4JpXfuNBg3csa/JnHt05vf+7/xNQGYdZxLJI X3XPLDyQk74JR3WlFHkre4QfXB+Tma4vgEPPTc0CLedi5ORwniF6yfWMy I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkEFAIC91VKtJV2Y/2dsb2JhbABagkdEOFa6b4EZFnSCJwECAi1eASpWJgEEGwEWh2UNmSSqbheOVoNcgRMEqjODLYIq X-IronPort-AV: E=Sophos;i="4.95,659,1384300800"; d="scan'208,217";a="12853020" Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-3.cisco.com with ESMTP; 14 Jan 2014 22:44:24 +0000 Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0EMiOiW003513 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 14 Jan 2014 22:44:24 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; Tue, 14 Jan 2014 16:44:24 -0600 From: "Bernie Volz (volz)" To: "dhcpv6bis@ietf.org" Thread-Topic: DHCPv6 BakeOffs in 2007/2008 Thread-Index: Ac8ReOasYeWjBKknSpSW4iVPlNNtqQ== Date: Tue, 14 Jan 2014 22:44:23 +0000 Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE1F185@xmb-rcd-x04.cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.86.242.7] Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1AE1F185xmbrcdx04ciscoc_" MIME-Version: 1.0 Subject: [Dhcpv6bis] DHCPv6 BakeOffs in 2007/2008 X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jan 2014 22:44:40 -0000 --_000_489D13FBFA9B3E41812EA89F188F018E1AE1F185xmbrcdx04ciscoc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi: There were 3 Comcast sponsored DHCPv6 bake-offs in 2007 and 2008. I've foun= d two presentations with the results from the events. http://www.ietf.org/proceedings/68/slides/dhc-8.pdf (1st, March 2007) http://www.ietf.org/proceedings/71/slides/dhc-10.pdf (3rd, March 2008) I haven't found one for the 2nd (which was just after the Vancouver IETF-70= ) so perhaps there was none (since the next was the March 2008). And, sadly= I don't have any good notes (at least that I've found so far) from that ev= ent. The IETF-71 presentation lists just one issue around Leasequery but doesn't= detail what the issue was. And, anyway, our DHCPv6bis work won't cover lea= sequery so it doesn't really matter. The IETF-68 presentation does list a bunch of issues (highest numbered is 1= 6). We probably should do through these and discuss ones to include in the = issues tracker. For example, Issue 7 is "Some clients use IAADDR with all z= ero to request specific lifetimes" (same goes for PD to request a prefix le= ngth). This behavior strictly speaking isn't documented in RFC 3315 so perh= aps it should be mentioned? I haven't reviewed the full list carefully and there may be some that requi= re a bit more discussion (perhaps even with DHC WG and/or including in the = stateful issues draft?) before accepting. --- I am also following up with Tim Winters for the UNH Interop. Lab as they ha= ve held various events (mostly for CableLabs interop testing) and also do c= ertification for DHCPv6 clients, relays, and servers. So he may have some u= seful items to include. Tomek is following up with CableLabs too. - Bernie --_000_489D13FBFA9B3E41812EA89F188F018E1AE1F185xmbrcdx04ciscoc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi:

 

There were 3 Comcast sponsored DHCPv6 bake-offs in 2= 007 and 2008. I’ve found two presentations with the results from the = events.

 

http://www.ietf.org/proceedings/68/slides/dhc-8.pdf (1= st, March 2007)

http://www.ietf.org/proceedings/71/slides/dhc-10.pdf (3rd,= March 2008)

 

I haven’t found one for the 2nd (wh= ich was just after the Vancouver IETF-70) so perhaps there was none (since = the next was the March 2008). And, sadly I don’t have any good notes = (at least that I’ve found so far) from that event.

 

The IETF-71 presentation lists just one issue around= Leasequery but doesn’t detail what the issue was. And, anyway, our D= HCPv6bis work won’t cover leasequery so it doesn’t really matte= r.

 

The IETF-68 presentation does list a bunch of issues= (highest numbered is 16). We probably should do through these and discuss = ones to include in the issues tracker. For example, Issue 7 is “Some = clients use IAADDR with all zero to request specific lifetimes” (same goes for PD to request a prefix length). T= his behavior strictly speaking isn’t documented in RFC 3315 so perhap= s it should be mentioned?

 

I haven’t reviewed the full list carefully and= there may be some that require a bit more discussion (perhaps even with DH= C WG and/or including in the stateful issues draft?) before accepting.=

 

---

 

I am also following up with Tim Winters for the UNH = Interop. Lab as they have held various events (mostly for CableLabs interop= testing) and also do certification for DHCPv6 clients, relays, and servers= . So he may have some useful items to include. Tomek is following up with CableLabs too.

 

-     &= nbsp;    Bernie

 

 

 

--_000_489D13FBFA9B3E41812EA89F188F018E1AE1F185xmbrcdx04ciscoc_-- From tomasz.mrugalski@gmail.com Mon Jan 20 10:43:22 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AFDA1A021A for ; Mon, 20 Jan 2014 10:43:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4 X-Spam-Level: X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_INVITATION=-2, SPF_PASS=-0.001] 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 KaeitpS3YJ1w for ; Mon, 20 Jan 2014 10:43:20 -0800 (PST) Received: from mail-ee0-x22e.google.com (mail-ee0-x22e.google.com [IPv6:2a00:1450:4013:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA901A022C for ; Mon, 20 Jan 2014 10:43:20 -0800 (PST) Received: by mail-ee0-f46.google.com with SMTP id c13so3529434eek.19 for ; Mon, 20 Jan 2014 10:43:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=iY76OFznUIJzozspTmcpOUWDb+/kg8GEQeVuzDJXRe8=; b=Q113WgwcG5Z9SIbo1xbLf6hg5RtaPykMryiga5BHzzZPtRG7KqVG4A/dmwhHcTmFZA F6rw3y5F7CqeLO6bUu2j32O0F378TaRmBsV2YDV6IVxG6bYPlw5LMo0LAhjWH1s8NRd/ ALes+/3/2G7lV5uf6Fg62UhmiZNJUS4H3KHF45nr3oZJrGcqli5DJNn3fukr9YIVvXnY 5efrRf7+CBf8REUYneZ5sLXXyZqRUiH2XTq+dEhS2wt2rU4BrWC6Sd+UXSaXcOrndzll 4+Bk8UIJeg3mr5JJiewWv9Yw/c/Z29W+wE6S76nxximzTuWPGt+P9SMVS8kg+TPcOers cI5w== X-Received: by 10.15.53.129 with SMTP id r1mr121752eew.111.1390243400103; Mon, 20 Jan 2014 10:43:20 -0800 (PST) Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id d43sm5952651eeo.12.2014.01.20.10.43.18 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 Jan 2014 10:43:19 -0800 (PST) Message-ID: <52DD6E41.7080708@gmail.com> Date: Mon, 20 Jan 2014 19:43:13 +0100 From: Tomek Mrugalski User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: dhcpv6bis@ietf.org References: <489D13FBFA9B3E41812EA89F188F018E1AE2AB2E@xmb-rcd-x04.cisco.com> In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AE2AB2E@xmb-rcd-x04.cisco.com> X-Enigmail-Version: 1.5.2 X-TagToolbar-Keys: D20140120194313064 X-Forwarded-Message-Id: <489D13FBFA9B3E41812EA89F188F018E1AE2AB2E@xmb-rcd-x04.cisco.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Dhcpv6bis] Agenda for dhcpv6bis meeting on 2014-01-22 X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jan 2014 18:43:22 -0000 Folks, Here's an agenda for upcoming Wednesday, Jan 22nd meeting 8:00 EST (14:00 CET, 21:00 CST). Bernie sent out meeting invitation in a separate mail. 1. Confirm that XML for 3315 is done. One outstanding issue are the cross-references. Bernie said he'll look at that. So this is likely to be a very quick item. 2. Confirm that XML for 3633 is done. Same as above, except we won't need cross-references as the text will end up being copied over to 3315bis, so its references will need to be tweaked anyway. 3. Get over the list of RFCs we want to merge. Tomek will send out a list of candidates. We'll decide for each of them what to do: a) reference only b) copy minimal text (e.g. UUID duid type) and reference the RFC/I-D c) skip completely 4. Discuss authorship The problem is with the number of authors. RFC Editor recommends to not have more than 5 authors (http://www.rfc-editor.org/policy.html#policy.authlist). This is a soft limit, so we can go over if needed, but going for full list (6 original 3315 authors + 5 new ones) will likely not be acceptable. Bernie proposed (and Tomek agrees) to go with the list of DHCPv6bis team members and thank 3315 authors in acknowledgement section. We will also want to thank some people that reported errata or issues. 5. Decide on next steps Proposal: - go over reported issues in the tracker. Segregate them into: a) obvious/easy to do => apply them before merge b) widely supported, but harder to do => apply them after merge c) contentious => leave them for discussion on DHC WG - apply/close issues marked as a) - upload new revision - merge - upload new revision - apply/close issues makred as b) - request adoption in DHC - discuss issues from c) group on DHC WG, get consensus on them, apply or reject on a per case basis - WGLC once all issues are closed 6. Go over reported issues in issue tracker and split into groups. We'll likely to assign owner to each issue. Such owner will be responsible for dealing with the issue (and lead any discussions that may emerge). 7. Any other business It seems that the majority of the time spent on the meeting will be about going through the issues in issue tracker. Please take a look at them prior to the meeting, if possible. Folks, keep in mind that this is very late meeting for Sheng, so please keep the non-essential stuff to minimum. Bernie & Tomek From volz@cisco.com Mon Jan 20 10:47:49 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92F201A0239 for ; Mon, 20 Jan 2014 10:47:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.035 X-Spam-Level: X-Spam-Status: No, score=-17.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 81G3ByogfyPK for ; Mon, 20 Jan 2014 10:47:46 -0800 (PST) Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 32CBE1A0232 for ; Mon, 20 Jan 2014 10:47:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25932; q=dns/txt; s=iport; t=1390243666; x=1391453266; h=from:to:cc:subject:date:message-id:mime-version; bh=8xfjg+g0fy/AcTmpLNtzrRkn4jFhSGcDJVj9S2SIFj8=; b=LQCVrYUmzlKDDlAvKLQCF1JoM02mjEDJ6cEn7r5eqA3OhHWZAhBYbC2Z CXLfr0zN8fWYcMYlmSa2AUAzLpLKCCN/YKI1aQMxuQHZ9aDekzf9HQx2g 23iwtG8VYNufC5QOyvRLTs/yjYEwrAo7Ln/ZNiPQRp1LeBl2I8b9HcJk/ o=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhgFANlu3VKtJXG//2dsb2JhbAA/FwOCR0Q4VoJ9uFYYeBZ0gicBBCMKKBETEgEqCgQSAgQwJAIBAQMODYd9DTanMJwDF44oBgEBCxMWCwwEEAgHglc1gRQEhVeDOJBFkGaCW1KBaQgXIg X-IronPort-AV: E=Sophos;i="4.95,691,1384300800"; d="scan'208,217";a="298586985" Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-4.cisco.com with ESMTP; 20 Jan 2014 18:47:43 +0000 Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0KIlhAq024512 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 20 Jan 2014 18:47:43 GMT Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.03.0123.003; Mon, 20 Jan 2014 12:47:42 -0600 From: "Bernie Volz (volz)" To: "dhcpv6bis@ietf.org" Thread-Topic: DHCPv6bis Team Meeting - Next Steps Thread-Index: Ac8QieqpXhkOFfVxRXyHNgY4uAgDuAFhi38Q Date: Mon, 20 Jan 2014 18:47:42 +0000 Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE2B112@xmb-rcd-x04.cisco.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: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1AE2B112xmbrcdx04ciscoc_" MIME-Version: 1.0 Cc: "tomasz.mrugalski@gmail.com" , 'Leaf Yeh' Subject: [Dhcpv6bis] DHCPv6bis Team Meeting - Next Steps X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jan 2014 18:47:49 -0000 --_000_489D13FBFA9B3E41812EA89F188F018E1AE2B112xmbrcdx04ciscoc_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Discuss how to proceed with applying issues and merging 3633 (and whatever = else). Please be sure to add items to the issue tracker! Updated with Agenda: Folks, Here's an agenda for upcoming Wednesday, Jan 22nd meeting 8:00 EST (14:00 CET, 21:00 CST). Bernie sent out meeting invitation in a se= parate mail. 1. Confirm that XML for 3315 is done. One outstanding issue are the cross-references. Bernie said he'll look at t= hat. So this is likely to be a very quick item. 2. Confirm that XML for 3633 is done. Same as above, except we won't need cross-references as the text will end u= p being copied over to 3315bis, so its references will need to be tweaked a= nyway. 3. Get over the list of RFCs we want to merge. Tomek will send out a list of candidates. We'll decide for each of them wha= t to do: a) reference only b) copy minimal text (e.g. UUID duid type) and reference the RFC/I-D c) skip completely 4. Discuss authorship The problem is with the number of authors. RFC Editor recommends to not hav= e more than 5 authors (http://www.rfc-editor.org/policy.html#policy.authlis= t). This is a soft limit, so we can go over if needed, but going for full l= ist (6 original 3315 authors + 5 new ones) will likely not be acceptable. Bernie proposed (= and Tomek agrees) to go with the list of DHCPv6bis team members and thank 3= 315 authors in acknowledgement section. We will also want to thank some peo= ple that reported errata or issues. 5. Decide on next steps Proposal: - go over reported issues in the tracker. Segregate them into: a) obvious/easy to do =3D> apply them before merge b) widely supported, but harder to do =3D> apply them after merge c) contentious =3D> leave them for discussion on DHC WG - apply/close issues marked as a) - upload new revision - merge - upload new revision - apply/close issues makred as b) - request adoption in DHC - discuss issues from c) group on DHC WG, get consensus on them, apply or reject on a per case basis - WGLC once all issues are closed 6. Go over reported issues in issue tracker and split into groups. We'll likely to assign owner to each issue. Such owner will be responsible = for dealing with the issue (and lead any discussions that may emerge). 7. Any other business It seems that the majority of the time spent on the meeting will be about g= oing through the issues in issue tracker. Please take a look at them prior = to the meeting, if possible. Folks, keep in mind that this is very late meeting for Sheng, so please kee= p the non-essential stuff to minimum. Bernie & Tomek ******* DO NOT DELETE OR CHANGE ANY OF THE TEXT BELOW THIS LINE ******* ----------------------------------------------------------------------- JOIN USING WebEx Go To: https://cisco.webex.com/cisco/j.php?J=3D204539449&PW=3DNNzJlYzE3MTk3 Meeting Password ----- 3315 Meeting Number ----- 204 539 449 ---------------------------------------------------------------- ALERT - PLEASE READ: DO NOT DIAL THE TOLL FREE NUMBERS FROM WITHIN THE (408= ) OR (919) AREA CODES ---------------------------------------------------------------- Please dial the local access number for your area from the list below: - San Jose/Milpitas (408) area: 525-6800 - RTP (919) area: 392-3330 Dialing the WebEx toll free numbers from within 408 or 919 area codes is no= t enabled (non-Cisco phones). " If you dial the toll-free numbers within t= he 408 or 919 area codes you will be instructed to hang up and dial the loc= al access number." Please use the call-back option whenever possible and ot= herwise dial local numbers only. The affected toll free numbers are: (866)= 432-9903 for the San Jose/Milpitas area and (866) 349-3520 for the RTP are= a. ------------------------------------------------------- To join the teleconference only ------------------------------------------------------- 1. Dial into Cisco WebEx (view all Global Access Numbers at http://cisco.com/en/US/about/doing_business/conferencing/index.html 2. Follow the prompts to enter the Meeting Number (listed above) or Access = Code followed by the # sign. San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330 US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117 India: +91.80.4350.1111 Germany: +49.619.6773.9002 Japan: +81.3.5763.9394 China: +86.10.8515.5666 IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a= nd any documents and other materials exchanged or viewed during the session= to be recorded. By joining this session, you automatically consent to such= recordings. If you do not consent to the recording, discuss your concerns = with the meeting host prior to the start of the recording or do not join th= e session. Please note that any such recordings may be subject to discovery= in the event of litigation. http://www.webex.com --_000_489D13FBFA9B3E41812EA89F188F018E1AE2B112xmbrcdx04ciscoc_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Discuss how to proceed with applying issues and merging 3633 (and what= ever else). Please be sure to add items to the issue tracker!
 
Updated with Agenda:
 
Folks,<= /div>
Here's an agenda for = upcoming Wednesday, Jan 22nd meeting
8:00 EST (14:00 CET, = 21:00 CST). Bernie sent out meeting invitation in a separate mail.
 <= /div>
1. Confirm that XML f= or 3315 is done.
One outstanding issue= are the cross-references. Bernie said he'll look at that. So this is likel= y to be a very quick item.
 <= /div>
2. Confirm that XML f= or 3633 is done.
Same as above, except= we won't need cross-references as the text will end up being copied over t= o 3315bis, so its references will need to be tweaked anyway.<= /div>
 <= /div>
3. Get over the list = of RFCs we want to merge.
Tomek will send out a= list of candidates. We'll decide for each of them what to do:
a) reference only
b) copy minimal text = (e.g. UUID duid type) and reference the RFC/I-D
c) skip completely
 <= /div>
4. Discuss authorship=
The problem is with t= he number of authors. RFC Editor recommends to not have more than 5 authors= (http://www.rfc-editor.org/policy.html#policy.authlist<= /font>). This is a soft limit, so we can go over if needed, but going for full list = (6 original
3315 authors + 5 = new ones) will likely not be acceptable. Bernie proposed (and Tomek agrees)= to go with the list of DHCPv6bis team members and thank 3315 authors in ac= knowledgement section. We will also want to thank some people that reported errata or issues.
 <= /div>
5. Decide on next ste= ps
Proposal:
 <= /div>
- go over reported is= sues in the tracker. Segregate them into:
  a) obvious/eas= y to do =3D> apply them before merge
  b) widely supp= orted, but harder to do =3D> apply them after merge
  c) contentious= =3D> leave them for discussion on DHC WG
 <= /div>
- apply/close issues = marked as a)
- upload new revision=
- merge=
- upload new revision=
- apply/close issues = makred as b)
- request adoption in= DHC
- discuss issues from= c) group on DHC WG, get consensus on them,
  apply or rejec= t on a per case basis
- WGLC once all issue= s are closed
 <= /div>
6. Go over reported i= ssues in issue tracker and split into groups.
 <= /div>
We'll likely to assig= n owner to each issue. Such owner will be responsible for dealing with the = issue (and lead any discussions that may emerge).
 <= /div>
7. Any other business=
 <= /div>
It seems that the maj= ority of the time spent on the meeting will be about going through the issu= es in issue tracker. Please take a look at them prior to the meeting, if po= ssible.
 <= /div>
Folks, keep in mind t= hat this is very late meeting for Sheng, so please keep the non-essential s= tuff to minimum.
 <= /div>
Bernie & Tomek
 
 
******* DO NOT DELETE OR CHANGE ANY= OF THE TEXT BELOW THIS LINE *******
 
----------------------------------------------------------------------= -
JOIN USING WebEx
 
Go To:
 <= /div>
Meeting Password ----- 3315
Meeting Number ----- 204 539 449
 
----------------------------------------------------------------
ALERT – PLEASE READ: DO NOT DIAL THE TOLL FREE NUMBERS FROM WITH= IN THE (408) OR (919) AREA CODES
----------------------------------------------------------------
Please dial the local access number for your area from the list below:=
-  San Jose/Milpitas (408) area:  525-6800
-  RTP (919) area:  392-3330
 
Dialing the WebEx toll free numbers from within 408 or 919 area codes = is not enabled (non-Cisco phones).  “ If you dial the toll-free = numbers within the 408 or 919 area codes you will be instructed to hang up = and dial the local access number.” Please use the call-back option whenever possible and otherwise dial local numbers onl= y.  The affected toll free numbers are: (866) 432-9903 for the San Jos= e/Milpitas area and (866) 349-3520 for the RTP area.
 
-------------------------------------------------------
To join the teleconference only
-------------------------------------------------------
1. Dial into Cisco WebEx (view all Global Access Numbers at
2. Follow the prompts to enter the Meeting Number (listed above) or Ac= cess Code followed by the # sign.
 
San Jose, CA: +1.408.525.6800  RTP: +1.919.392.3330
 
US/Canada: +1.866.432.9903  United Kingdom: +44.20.8824.0= 117
 
India: +91.80.4350.1111  Germany: +49.619.6773.9002
 
Japan: +81.3.5763.9394  China: +86.10.8515.5666
 
IMPORTANT NOTICE: This WebEx service includes a feature that allows au= dio and any documents and other materials exchanged or viewed during the se= ssion to be recorded. By joining this session, you automatically consent to= such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior= to the start of the recording or do not join the session. Please note that= any such recordings may be subject to discovery in the event of litigation= .
 
    
 
 <= /div> --_000_489D13FBFA9B3E41812EA89F188F018E1AE2B112xmbrcdx04ciscoc_ Content-Type: text/calendar; charset="utf-8"; method=REQUEST Content-Transfer-Encoding: base64 QkVHSU46VkNBTEVOREFSDQpNRVRIT0Q6UkVRVUVTVA0KUFJPRElEOk1pY3Jvc29mdCBFeGNoYW5n ZSBTZXJ2ZXIgMjAxMA0KVkVSU0lPTjoyLjANCkJFR0lOOlZUSU1FWk9ORQ0KVFpJRDpFYXN0ZXJu IFN0YW5kYXJkIFRpbWUNCkJFR0lOOlNUQU5EQVJEDQpEVFNUQVJUOjE2MDEwMTAxVDAyMDAwMA0K VFpPRkZTRVRGUk9NOi0wNDAwDQpUWk9GRlNFVFRPOi0wNTAwDQpSUlVMRTpGUkVRPVlFQVJMWTtJ TlRFUlZBTD0xO0JZREFZPTFTVTtCWU1PTlRIPTExDQpFTkQ6U1RBTkRBUkQNCkJFR0lOOkRBWUxJ R0hUDQpEVFNUQVJUOjE2MDEwMTAxVDAyMDAwMA0KVFpPRkZTRVRGUk9NOi0wNTAwDQpUWk9GRlNF VFRPOi0wNDAwDQpSUlVMRTpGUkVRPVlFQVJMWTtJTlRFUlZBTD0xO0JZREFZPTJTVTtCWU1PTlRI PTMNCkVORDpEQVlMSUdIVA0KRU5EOlZUSU1FWk9ORQ0KQkVHSU46VkVWRU5UDQpPUkdBTklaRVI7 Q049QmVybmllIFZvbHogKHZvbHopOk1BSUxUTzp2b2x6QGNpc2NvLmNvbQ0KQVRURU5ERUU7Uk9M RT1SRVEtUEFSVElDSVBBTlQ7UEFSVFNUQVQ9TkVFRFMtQUNUSU9OO1JTVlA9VFJVRTtDTj1kaGNw djZiaXNADQogaWV0Zi5vcmc6TUFJTFRPOmRoY3B2NmJpc0BpZXRmLm9yZw0KQVRURU5ERUU7Uk9M RT1PUFQtUEFSVElDSVBBTlQ7UEFSVFNUQVQ9TkVFRFMtQUNUSU9OO1JTVlA9VFJVRTtDTj0nTGVh ZiBZZWgnDQogOk1BSUxUTzpsZWFmLnllaC5zZG9AZ21haWwuY29tDQpBVFRFTkRFRTtST0xFPU9Q VC1QQVJUSUNJUEFOVDtQQVJUU1RBVD1ORUVEUy1BQ1RJT047UlNWUD1UUlVFO0NOPXRvbWFzei5t cnUNCiBnYWxza2lAZ21haWwuY29tOk1BSUxUTzp0b21hc3oubXJ1Z2Fsc2tpQGdtYWlsLmNvbQ0K REVTQ1JJUFRJT047TEFOR1VBR0U9ZW4tVVM6RGlzY3VzcyBob3cgdG8gcHJvY2VlZCB3aXRoIGFw cGx5aW5nIGlzc3VlcyBhbmQgDQogbWVyZ2luZyAzNjMzIChhbmQgd2hhdGV2ZXIgZWxzZSkuIFBs ZWFzZSBiZSBzdXJlIHRvIGFkZCBpdGVtcyB0byB0aGUgaXNzdWUNCiAgdHJhY2tlciFcblxuVXBk YXRlZCB3aXRoIEFnZW5kYTpcblxuRm9sa3NcLFxuSGVyZSdzIGFuIGFnZW5kYSBmb3IgdXBjb21p bg0KIGcgV2VkbmVzZGF5XCwgSmFuIDIybmQgbWVldGluZ1xuODowMCBFU1QgKDE0OjAwIENFVFws IDIxOjAwIENTVCkuIEJlcm5pZSBzDQogZW50IG91dCBtZWV0aW5nIGludml0YXRpb24gaW4gYSBz ZXBhcmF0ZSBtYWlsLlxuXG4xLiBDb25maXJtIHRoYXQgWE1MIGZvciANCiAzMzE1IGlzIGRvbmUu XG5PbmUgb3V0c3RhbmRpbmcgaXNzdWUgYXJlIHRoZSBjcm9zcy1yZWZlcmVuY2VzLiBCZXJuaWUg c2FpZA0KICBoZSdsbCBsb29rIGF0IHRoYXQuIFNvIHRoaXMgaXMgbGlrZWx5IHRvIGJlIGEgdmVy eSBxdWljayBpdGVtLlxuXG4yLiBDb25mDQogaXJtIHRoYXQgWE1MIGZvciAzNjMzIGlzIGRvbmUu XG5TYW1lIGFzIGFib3ZlXCwgZXhjZXB0IHdlIHdvbid0IG5lZWQgY3Jvc3MNCiAtcmVmZXJlbmNl cyBhcyB0aGUgdGV4dCB3aWxsIGVuZCB1cCBiZWluZyBjb3BpZWQgb3ZlciB0byAzMzE1YmlzXCwg c28gaXRzIA0KIHJlZmVyZW5jZXMgd2lsbCBuZWVkIHRvIGJlIHR3ZWFrZWQgYW55d2F5LlxuXG4z LiBHZXQgb3ZlciB0aGUgbGlzdCBvZiBSRkNzDQogIHdlIHdhbnQgdG8gbWVyZ2UuXG5Ub21layB3 aWxsIHNlbmQgb3V0IGEgbGlzdCBvZiBjYW5kaWRhdGVzLiBXZSdsbCBkZWNpZGUNCiAgZm9yIGVh Y2ggb2YgdGhlbSB3aGF0IHRvIGRvOlxuYSkgcmVmZXJlbmNlIG9ubHlcbmIpIGNvcHkgbWluaW1h bCB0ZXh0IChlLg0KIGcuIFVVSUQgZHVpZCB0eXBlKSBhbmQgcmVmZXJlbmNlIHRoZSBSRkMvSS1E XG5jKSBza2lwIGNvbXBsZXRlbHlcblxuNC4gRGlzDQogY3VzcyBhdXRob3JzaGlwXG5UaGUgcHJv YmxlbSBpcyB3aXRoIHRoZSBudW1iZXIgb2YgYXV0aG9ycy4gUkZDIEVkaXRvciByZWMNCiBvbW1l bmRzIHRvIG5vdCBoYXZlIG1vcmUgdGhhbiA1IGF1dGhvcnMgKGh0dHA6Ly93d3cucmZjLWVkaXRv ci5vcmcvcG9saWN5Lg0KIGh0bWwjcG9saWN5LmF1dGhsaXN0KS4gVGhpcyBpcyBhIHNvZnQgbGlt aXRcLCBzbyB3ZSBjYW4gZ28gb3ZlciBpZiBuZWVkZWRcDQogLCBidXQgZ29pbmcgZm9yIGZ1bGwg bGlzdCAoNiBvcmlnaW5hbFxuMzMxNSBhdXRob3JzICsgNSBuZXcgb25lcykgd2lsbCBsaWsNCiBl bHkgbm90IGJlIGFjY2VwdGFibGUuIEJlcm5pZSBwcm9wb3NlZCAoYW5kIFRvbWVrIGFncmVlcykg dG8gZ28gd2l0aCB0aGUgbA0KIGlzdCBvZiBESENQdjZiaXMgdGVhbSBtZW1iZXJzIGFuZCB0aGFu ayAzMzE1IGF1dGhvcnMgaW4gYWNrbm93bGVkZ2VtZW50IHNlDQogY3Rpb24uIFdlIHdpbGwgYWxz byB3YW50IHRvIHRoYW5rIHNvbWUgcGVvcGxlIHRoYXQgcmVwb3J0ZWQgZXJyYXRhIG9yIGlzc3UN CiBlcy5cblxuNS4gRGVjaWRlIG9uIG5leHQgc3RlcHNcblByb3Bvc2FsOlxuXG4tIGdvIG92ZXIg cmVwb3J0ZWQgaXNzdWVzIGluIA0KIHRoZSB0cmFja2VyLiBTZWdyZWdhdGUgdGhlbSBpbnRvOlxu ICBhKSBvYnZpb3VzL2Vhc3kgdG8gZG8gPT4gYXBwbHkgdGhlbSBiDQogZWZvcmUgbWVyZ2VcbiAg Yikgd2lkZWx5IHN1cHBvcnRlZFwsIGJ1dCBoYXJkZXIgdG8gZG8gPT4gYXBwbHkgdGhlbSBhZnRl ciANCiBtZXJnZVxuICBjKSBjb250ZW50aW91cyA9PiBsZWF2ZSB0aGVtIGZvciBkaXNjdXNzaW9u IG9uIERIQyBXR1xuXG4tIGFwcGx5Lw0KIGNsb3NlIGlzc3VlcyBtYXJrZWQgYXMgYSlcbi0gdXBs b2FkIG5ldyByZXZpc2lvblxuLSBtZXJnZVxuLSB1cGxvYWQgbmV3IHJlDQogdmlzaW9uXG4tIGFw cGx5L2Nsb3NlIGlzc3VlcyBtYWtyZWQgYXMgYilcbi0gcmVxdWVzdCBhZG9wdGlvbiBpbiBESENc bi0gZGkNCiBzY3VzcyBpc3N1ZXMgZnJvbSBjKSBncm91cCBvbiBESEMgV0dcLCBnZXQgY29uc2Vu c3VzIG9uIHRoZW1cLFxuICBhcHBseSBvcg0KICByZWplY3Qgb24gYSBwZXIgY2FzZSBiYXNpc1xu LSBXR0xDIG9uY2UgYWxsIGlzc3VlcyBhcmUgY2xvc2VkXG5cbjYuIEdvIG92DQogZXIgcmVwb3J0 ZWQgaXNzdWVzIGluIGlzc3VlIHRyYWNrZXIgYW5kIHNwbGl0IGludG8gZ3JvdXBzLlxuXG5XZSds bCBsaWtlbHkNCiAgdG8gYXNzaWduIG93bmVyIHRvIGVhY2ggaXNzdWUuIFN1Y2ggb3duZXIgd2ls bCBiZSByZXNwb25zaWJsZSBmb3IgZGVhbGluZw0KICB3aXRoIHRoZSBpc3N1ZSAoYW5kIGxlYWQg YW55IGRpc2N1c3Npb25zIHRoYXQgbWF5IGVtZXJnZSkuXG5cbjcuIEFueSBvdGhlDQogciBidXNp bmVzc1xuXG5JdCBzZWVtcyB0aGF0IHRoZSBtYWpvcml0eSBvZiB0aGUgdGltZSBzcGVudCBvbiB0 aGUgbWVldGluZyANCiB3aWxsIGJlIGFib3V0IGdvaW5nIHRocm91Z2ggdGhlIGlzc3VlcyBpbiBp c3N1ZSB0cmFja2VyLiBQbGVhc2UgdGFrZSBhIGxvbw0KIGsgYXQgdGhlbSBwcmlvciB0byB0aGUg bWVldGluZ1wsIGlmIHBvc3NpYmxlLlxuXG5Gb2xrc1wsIGtlZXAgaW4gbWluZCB0aGF0DQogIHRo aXMgaXMgdmVyeSBsYXRlIG1lZXRpbmcgZm9yIFNoZW5nXCwgc28gcGxlYXNlIGtlZXAgdGhlIG5v bi1lc3NlbnRpYWwgc3QNCiB1ZmYgdG8gbWluaW11bS5cblxuQmVybmllICYgVG9tZWtcblxuXG4q KioqKioqIERPIE5PVCBERUxFVEUgT1IgQ0hBTkdFIEFOWQ0KICBPRiBUSEUgVEVYVCBCRUxPVyBU SElTIExJTkUgKioqKioqKlxuXG4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQog LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLVxuSk9JTiBVU0lORyBXZWJFeFxu XG5HbyBUbzpcbmh0dHBzOi8NCiAvY2lzY28ud2ViZXguY29tL2Npc2NvL2oucGhwP0o9MjA0NTM5 NDQ5JlBXPU5OekpsWXpFM01UazNcblxuTWVldGluZyBQYXNzdw0KIG9yZCAtLS0tLSAzMzE1XG5N ZWV0aW5nIE51bWJlciAtLS0tLSAyMDQgNTM5IDQ0OVxuXG4tLS0tLS0tLS0tLS0tLS0tLS0tLS0t DQogLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tXG5BTEVSVCDigJMg UExFQVNFIFJFQUQ6IERPIE5PVCANCiBESUFMIFRIRSBUT0xMIEZSRUUgTlVNQkVSUyBGUk9NIFdJ VEhJTiBUSEUgKDQwOCkgT1IgKDkxOSkgQVJFQSBDT0RFU1xuLS0tLQ0KIC0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLVxuUGxlYXNlIGRp YWwgDQogdGhlIGxvY2FsIGFjY2VzcyBudW1iZXIgZm9yIHlvdXIgYXJlYSBmcm9tIHRoZSBsaXN0 IGJlbG93OlxuLSAgU2FuIEpvc2UvTWkNCiBscGl0YXMgKDQwOCkgYXJlYTogIDUyNS02ODAwXG4t ICBSVFAgKDkxOSkgYXJlYTogIDM5Mi0zMzMwXG5cbkRpYWxpbmcgdGhlIA0KIFdlYkV4IHRvbGwg ZnJlZSBudW1iZXJzIGZyb20gd2l0aGluIDQwOCBvciA5MTkgYXJlYSBjb2RlcyBpcyBub3QgZW5h YmxlZCAoDQogbm9uLUNpc2NvIHBob25lcykuICDigJwgSWYgeW91IGRpYWwgdGhlIHRvbGwtZnJl ZSBudW1iZXJzIHdpdGhpbiB0aGUgNDA4IG8NCiByIDkxOSBhcmVhIGNvZGVzIHlvdSB3aWxsIGJl IGluc3RydWN0ZWQgdG8gaGFuZyB1cCBhbmQgZGlhbCB0aGUgbG9jYWwgYWNjZQ0KIHNzIG51bWJl ci7igJ0gUGxlYXNlIHVzZSB0aGUgY2FsbC1iYWNrIG9wdGlvbiB3aGVuZXZlciBwb3NzaWJsZSBh bmQgb3RoZXJ3DQogaXNlIGRpYWwgbG9jYWwgbnVtYmVycyBvbmx5LiAgVGhlIGFmZmVjdGVkIHRv bGwgZnJlZSBudW1iZXJzIGFyZTogKDg2NikgNDMNCiAyLTk5MDMgZm9yIHRoZSBTYW4gSm9zZS9N aWxwaXRhcyBhcmVhIGFuZCAoODY2KSAzNDktMzUyMCBmb3IgdGhlIFJUUCBhcmVhLg0KIFxuXG4t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tXG5U byBqb2luIHRoZSB0DQogZWxlY29uZmVyZW5jZSBvbmx5XG4tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCiAtXG4xLiBEaWFsIGludG8gQ2lzY28g V2ViRXggKHZpZXcgYWxsIEdsb2JhbCBBY2Nlc3MgTnVtYmVycyBhdFxuaHR0cDovL2Npcw0KIGNv LmNvbS9lbi9VUy9hYm91dC9kb2luZ19idXNpbmVzcy9jb25mZXJlbmNpbmcvaW5kZXguaHRtbFxu Mi4gRm9sbG93IHRoZSBwDQogcm9tcHRzIHRvIGVudGVyIHRoZSBNZWV0aW5nIE51bWJlciAobGlz dGVkIGFib3ZlKSBvciBBY2Nlc3MgQ29kZSBmb2xsb3dlZCANCiBieSB0aGUgIyBzaWduLlxuXG5T YW4gSm9zZVwsIENBOiArMS40MDguNTI1LjY4MDAgIFJUUDogKzEuOTE5LjM5Mi4zMzMwXG5cbg0K IFVTL0NhbmFkYTogKzEuODY2LjQzMi45OTAzICBVbml0ZWQgS2luZ2RvbTogKzQ0LjIwLjg4MjQu MDExN1xuXG5JbmRpYTogKzkxDQogLjgwLjQzNTAuMTExMSAgR2VybWFueTogKzQ5LjYxOS42Nzcz LjkwMDJcblxuSmFwYW46ICs4MS4zLjU3NjMuOTM5NCAgQ2hpbmENCiA6ICs4Ni4xMC44NTE1LjU2 NjZcblxuSU1QT1JUQU5UIE5PVElDRTogVGhpcyBXZWJFeCBzZXJ2aWNlIGluY2x1ZGVzIGEgZmVh dA0KIHVyZSB0aGF0IGFsbG93cyBhdWRpbyBhbmQgYW55IGRvY3VtZW50cyBhbmQgb3RoZXIgbWF0 ZXJpYWxzIGV4Y2hhbmdlZCBvciB2DQogaWV3ZWQgZHVyaW5nIHRoZSBzZXNzaW9uIHRvIGJlIHJl Y29yZGVkLiBCeSBqb2luaW5nIHRoaXMgc2Vzc2lvblwsIHlvdSBhdXQNCiBvbWF0aWNhbGx5IGNv bnNlbnQgdG8gc3VjaCByZWNvcmRpbmdzLiBJZiB5b3UgZG8gbm90IGNvbnNlbnQgdG8gdGhlIHJl Y29yZA0KIGluZ1wsIGRpc2N1c3MgeW91ciBjb25jZXJucyB3aXRoIHRoZSBtZWV0aW5nIGhvc3Qg cHJpb3IgdG8gdGhlIHN0YXJ0IG9mIHRoDQogZSByZWNvcmRpbmcgb3IgZG8gbm90IGpvaW4gdGhl IHNlc3Npb24uIFBsZWFzZSBub3RlIHRoYXQgYW55IHN1Y2ggcmVjb3JkaW4NCiBncyBtYXkgYmUg c3ViamVjdCB0byBkaXNjb3ZlcnkgaW4gdGhlIGV2ZW50IG9mIGxpdGlnYXRpb24uXG5cbmh0dHA6 Ly93d3cudw0KIGViZXguY29tXG5cblxuXG4NClNVTU1BUlk7TEFOR1VBR0U9ZW4tVVM6REhDUHY2 YmlzIFRlYW0gTWVldGluZyAtIE5leHQgU3RlcHMNCkRUU1RBUlQ7VFpJRD1FYXN0ZXJuIFN0YW5k YXJkIFRpbWU6MjAxNDAxMjJUMDgwMDAwDQpEVEVORDtUWklEPUVhc3Rlcm4gU3RhbmRhcmQgVGlt ZToyMDE0MDEyMlQwOTAwMDANClVJRDowNDAwMDAwMDgyMDBFMDAwNzRDNUI3MTAxQTgyRTAwODAw MDAwMDAwQTA1MzFGNEM2MDEwQ0YwMTAwMDAwMDAwMDAwMDAwMA0KIDAxMDAwMDAwMDhBNTZERjFG RDk0NzQzNDc5RDMxRjFCMjUxMzlGQTIxDQpDTEFTUzpQVUJMSUMNClBSSU9SSVRZOjUNCkRUU1RB TVA6MjAxNDAxMjBUMTg0NzQwWg0KVFJBTlNQOk9QQVFVRQ0KU1RBVFVTOkNPTkZJUk1FRA0KU0VR VUVOQ0U6MQ0KTE9DQVRJT047TEFOR1VBR0U9ZW4tVVM6V2ViRXgNClgtTUlDUk9TT0ZULUNETy1B UFBULVNFUVVFTkNFOjENClgtTUlDUk9TT0ZULUNETy1PV05FUkFQUFRJRDotMTIzNjQ2MTYwMg0K WC1NSUNST1NPRlQtQ0RPLUJVU1lTVEFUVVM6VEVOVEFUSVZFDQpYLU1JQ1JPU09GVC1DRE8tSU5U RU5ERURTVEFUVVM6QlVTWQ0KWC1NSUNST1NPRlQtQ0RPLUFMTERBWUVWRU5UOkZBTFNFDQpYLU1J Q1JPU09GVC1DRE8tSU1QT1JUQU5DRToxDQpYLU1JQ1JPU09GVC1DRE8tSU5TVFRZUEU6MA0KWC1N SUNST1NPRlQtRElTQUxMT1ctQ09VTlRFUjpGQUxTRQ0KQkVHSU46VkFMQVJNDQpBQ1RJT046RElT UExBWQ0KREVTQ1JJUFRJT046UkVNSU5ERVINClRSSUdHRVI7UkVMQVRFRD1TVEFSVDotUFQxNU0N CkVORDpWQUxBUk0NCkVORDpWRVZFTlQNCkVORDpWQ0FMRU5EQVINCg== --_000_489D13FBFA9B3E41812EA89F188F018E1AE2B112xmbrcdx04ciscoc_-- From tomasz.mrugalski@gmail.com Mon Jan 20 10:49:26 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8B341A023B for ; Mon, 20 Jan 2014 10:49:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4 X-Spam-Level: X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_INVITATION=-2, SPF_PASS=-0.001] 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 PtfjZ7qcQt5Q for ; Mon, 20 Jan 2014 10:49:24 -0800 (PST) Received: from mail-ea0-x22a.google.com (mail-ea0-x22a.google.com [IPv6:2a00:1450:4013:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5C5791A024C for ; Mon, 20 Jan 2014 10:49:22 -0800 (PST) Received: by mail-ea0-f170.google.com with SMTP id k10so3308472eaj.29 for ; Mon, 20 Jan 2014 10:49:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=CPZoTlxnD7XymqHImjXAOxDRmiN/j4C8Gn+CMbEoQYw=; b=E/xx1NuuoMYmWtYPdqKZKfqc0nsI2nRML+mgE2ytvtG+lsTnr6S5Ht47rPYFgbZLwJ MUSRtr2LRnaWPtutt0y6V8d0WJ1CoZdcSj/yMrQVFqzvGszYAoQE7UNRtnwL36VvEf0L vd9UhxEg31KToWy2wQr8HvyPtIun5aDAvdSw2ZcD/jtMXqh9LCGTLjXQp9I0THV1UWPk 4WBBYDCr//QqYjn2S9mLu452DiLT5Tk+/OOLyXEujiJD0cfwWagUrVKjoCHalcdOhrzH yxVZqUIJ2DxD9FiT0s/7xTubr8iORyuxtMnNl4Z+pBwi05IkoQidaX1yOXGQzJfdIUFP uKqg== X-Received: by 10.14.201.68 with SMTP id a44mr19419452eeo.46.1390243762080; Mon, 20 Jan 2014 10:49:22 -0800 (PST) Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id x1sm2524438een.17.2014.01.20.10.49.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 Jan 2014 10:49:21 -0800 (PST) Message-ID: <52DD6FAB.3090609@gmail.com> Date: Mon, 20 Jan 2014 19:49:15 +0100 From: Tomek Mrugalski User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: dhcpv6bis@ietf.org References: <489D13FBFA9B3E41812EA89F188F018E1AE2AB2E@xmb-rcd-x04.cisco.com> <52DD6E41.7080708@gmail.com> In-Reply-To: <52DD6E41.7080708@gmail.com> X-Enigmail-Version: 1.5.2 X-TagToolbar-Keys: D20140120194915446 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Dhcpv6bis] Agenda for dhcpv6bis meeting on 2014-01-22 X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jan 2014 18:49:27 -0000 Oops, Forgot about one extra item: X. Come up with the merge 3633/3315 strategy. This looks like a too big task for a single person, so we'll probably try to split this work among two volunteers. Haven't given much thought about how to do this, but each person being responsible for moving roughly a half of the 3633 sections seems like a good idea. Tomek On 20.01.2014 19:43, Tomek Mrugalski wrote: > Folks, > Here's an agenda for upcoming Wednesday, Jan 22nd meeting > 8:00 EST (14:00 CET, 21:00 CST). Bernie sent out meeting invitation in a > separate mail. > > 1. Confirm that XML for 3315 is done. > One outstanding issue are the cross-references. Bernie said he'll look > at that. So this is likely to be a very quick item. > > 2. Confirm that XML for 3633 is done. > Same as above, except we won't need cross-references as the text will > end up being copied over to 3315bis, so its references will need to be > tweaked anyway. > > 3. Get over the list of RFCs we want to merge. > Tomek will send out a list of candidates. We'll decide for each of them > what to do: > a) reference only > b) copy minimal text (e.g. UUID duid type) and reference the RFC/I-D > c) skip completely > > 4. Discuss authorship > The problem is with the number of authors. RFC Editor recommends to not > have more than 5 authors > (http://www.rfc-editor.org/policy.html#policy.authlist). This is a soft > limit, so we can go over if needed, but going for full list (6 original > 3315 authors + 5 new ones) will likely not be acceptable. Bernie > proposed (and Tomek agrees) to go with the list of DHCPv6bis team > members and thank 3315 authors in acknowledgement section. We will also > want to thank some people that reported errata or issues. > > 5. Decide on next steps > Proposal: > > - go over reported issues in the tracker. Segregate them into: > a) obvious/easy to do => apply them before merge > b) widely supported, but harder to do => apply them after merge > c) contentious => leave them for discussion on DHC WG > > - apply/close issues marked as a) > - upload new revision > - merge > - upload new revision > - apply/close issues makred as b) > - request adoption in DHC > - discuss issues from c) group on DHC WG, get consensus on them, > apply or reject on a per case basis > - WGLC once all issues are closed > > 6. Go over reported issues in issue tracker and split into groups. > > We'll likely to assign owner to each issue. Such owner will be > responsible for dealing with the issue (and lead any discussions that > may emerge). > > 7. Any other business > > It seems that the majority of the time spent on the meeting will be > about going through the issues in issue tracker. Please take a look at > them prior to the meeting, if possible. > > Folks, keep in mind that this is very late meeting for Sheng, so please > keep the non-essential stuff to minimum. > > Bernie & Tomek > From volz@cisco.com Tue Jan 21 08:21:32 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED1A61A02F2 for ; Tue, 21 Jan 2014 08:21:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -12.035 X-Spam-Level: X-Spam-Status: No, score=-12.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, 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 lKIbgTsIV9ac for ; Tue, 21 Jan 2014 08:21:29 -0800 (PST) Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) by ietfa.amsl.com (Postfix) with ESMTP id 71C9D1A0184 for ; Tue, 21 Jan 2014 08:21:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=35347; q=dns/txt; s=iport; t=1390321289; x=1391530889; h=from:to:subject:date:message-id:mime-version; bh=jw7jUTceCD8RTxNKrVGTYFFQrI4bUaGunh9nkLEhRd8=; b=FIKkv2ZVwrlnFS9yVuM8RyiHA7Y9kfwZaB6OLXS9dPqv+D3eHy3P7VrE UDXNbSpxgDU6yt6d7yjP/jKZvwjvrH5uP77cqoqrRA8RkDzwcWbsrUJfJ lsZjB8j8lMz0d1iDRY2uwIHWVbwlfsTVVathpmOqoAgFw9r6XOCp+nEGh I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjAFAAOe3lKtJXG9/2dsb2JhbAA/FwOCR0Q4VoJ9uHAYexZ0gicBBCMKKBElASoKBBICBDAkAgEBAxsGh3cNNpgPjxGcKBeOHQsFAgEKARMWCwsBHAeCVzWBFASFV4pkiRmQZoJbUoFpQQ X-IronPort-AV: E=Sophos;i="4.95,696,1384300800"; d="scan'208,217";a="14400738" Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by alln-iport-7.cisco.com with ESMTP; 21 Jan 2014 16:21:27 +0000 Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0LGLRSG030423 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 21 Jan 2014 16:21:27 GMT Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0123.003; Tue, 21 Jan 2014 10:21:27 -0600 From: "Bernie Volz (volz)" To: "dhcpv6bis@ietf.org" Thread-Topic: Reminder - WebEx "meeting" Wed 1/22 Thread-Index: Ac8WxE5D4ynVxUxbQX2uMf2uM1J/xw== Date: Tue, 21 Jan 2014 16:21:26 +0000 Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE2D20A@xmb-rcd-x04.cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [161.44.65.114] Content-Type: multipart/mixed; boundary="_004_489D13FBFA9B3E41812EA89F188F018E1AE2D20Axmbrcdx04ciscoc_" MIME-Version: 1.0 Subject: [Dhcpv6bis] Reminder - WebEx "meeting" Wed 1/22 X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 16:21:33 -0000 --_004_489D13FBFA9B3E41812EA89F188F018E1AE2D20Axmbrcdx04ciscoc_ Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1AE2D20Axmbrcdx04ciscoc_" --_000_489D13FBFA9B3E41812EA89F188F018E1AE2D20Axmbrcdx04ciscoc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi: Just a reminder that we'll have a WebEx meeting on 1/22 8 AM EST (US). Invite is attached if you didn't get it earlier. Andrew Y. will not be attending as he'll be in transit. He did say to assig= n him some action items :). I hope everyone else will be available. I still hope to add tickets for "new items" from: 1. The DHCPv6 bakeoff issues (sent email earlier) 2. Stateful Issues draft If anyone has time to do either of these before tomorrow morning, let me kn= ow. I did update the 3315bis document to include xrefs to section anchors so th= at if we add/remove sections, the references should be updated properly. - Bernie --_000_489D13FBFA9B3E41812EA89F188F018E1AE2D20Axmbrcdx04ciscoc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi:

 

Just a reminder that we’ll have a WebEx meetin= g on 1/22 8 AM EST (US).

 

Invite is attached if you didn’t get it earlie= r.

 

Andrew Y. will not be attending as he’ll be in= transit. He did say to assign him some action items J.

 

I hope everyone else will be available.

 

I still hope to add tickets for “new itemsR= 21; from:

1.     &= nbsp; The DHCPv6 bakeoff issues (sent email earlier)=

2.     &= nbsp; Stateful Issues draft

 

If anyone has time to do either of these before tomo= rrow morning, let me know.

 

I did update the 3315bis document to include xrefs t= o section anchors so that if we add/remove sections, the references should = be updated properly.

 

-     &= nbsp;    Bernie

--_000_489D13FBFA9B3E41812EA89F188F018E1AE2D20Axmbrcdx04ciscoc_-- --_004_489D13FBFA9B3E41812EA89F188F018E1AE2D20Axmbrcdx04ciscoc_ Content-Type: message/rfc822 Content-Disposition: attachment; creation-date="Tue, 21 Jan 2014 16:21:25 GMT"; modification-date="Tue, 21 Jan 2014 16:21:25 GMT" From: "Bernie Volz (volz)" To: "Bernie Volz (volz)" , "dhcpv6bis@ietf.org" CC: 'Leaf Yeh' , "tomasz.mrugalski@gmail.com" Subject: DHCPv6bis Team Meeting - Next Steps Thread-Index: Ac8QieqpXhkOFfVxRXyHNgY4uAgDuA== Date: Mon, 13 Jan 2014 18:06:39 +0000 Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE1B29C@xmb-rcd-x04.cisco.com> Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1AE1B29Cxmbrcdx04ciscoc_" MIME-Version: 1.0 --_000_489D13FBFA9B3E41812EA89F188F018E1AE1B29Cxmbrcdx04ciscoc_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Discuss how to proceed with applying issues and merging 3633 (and whatever = else). Please be sure to add items to the issue tracker! Updated with Agenda: Folks, Here's an agenda for upcoming Wednesday, Jan 22nd meeting 8:00 EST (14:00 CET, 21:00 CST). Bernie sent out meeting invitation in a se= parate mail. 1. Confirm that XML for 3315 is done. One outstanding issue are the cross-references. Bernie said he'll look at t= hat. So this is likely to be a very quick item. 2. Confirm that XML for 3633 is done. Same as above, except we won't need cross-references as the text will end u= p being copied over to 3315bis, so its references will need to be tweaked a= nyway. 3. Get over the list of RFCs we want to merge. Tomek will send out a list of candidates. We'll decide for each of them wha= t to do: a) reference only b) copy minimal text (e.g. UUID duid type) and reference the RFC/I-D c) skip completely 4. Discuss authorship The problem is with the number of authors. RFC Editor recommends to not hav= e more than 5 authors (http://www.rfc-editor.org/policy.html#policy.authlis= t). This is a soft limit, so we can go over if needed, but going for full l= ist (6 original 3315 authors + 5 new ones) will likely not be acceptable. Bernie proposed (= and Tomek agrees) to go with the list of DHCPv6bis team members and thank 3= 315 authors in acknowledgement section. We will also want to thank some peo= ple that reported errata or issues. 5. Decide on next steps Proposal: - go over reported issues in the tracker. Segregate them into: a) obvious/easy to do =3D> apply them before merge b) widely supported, but harder to do =3D> apply them after merge c) contentious =3D> leave them for discussion on DHC WG - apply/close issues marked as a) - upload new revision - merge - upload new revision - apply/close issues makred as b) - request adoption in DHC - discuss issues from c) group on DHC WG, get consensus on them, apply or reject on a per case basis - WGLC once all issues are closed 6. Go over reported issues in issue tracker and split into groups. We'll likely to assign owner to each issue. Such owner will be responsible = for dealing with the issue (and lead any discussions that may emerge). 7. Any other business It seems that the majority of the time spent on the meeting will be about g= oing through the issues in issue tracker. Please take a look at them prior = to the meeting, if possible. Folks, keep in mind that this is very late meeting for Sheng, so please kee= p the non-essential stuff to minimum. Bernie & Tomek -+-----+-----+-----+-----+-----+-----+-----+-----+- [Do not add or change anything below this line. The information in this sec= tion may be replaced with your meeting details after you click Send.] ******* DO NOT DELETE OR CHANGE ANY OF THE TEXT BELOW THIS LINE ******* ----------------------------------------------------------------------- JOIN USING WebEx Go To: https://cisco.webex.com/cisco/j.php?J=3D204539449&PW=3DNNzJlYzE3MTk3 Meeting Password ----- 3315 Meeting Number ----- 204 539 449 ---------------------------------------------------------------- ALERT =96 PLEASE READ: DO NOT DIAL THE TOLL FREE NUMBERS FROM WITHIN THE (4= 08) OR (919) AREA CODES ---------------------------------------------------------------- Please dial the local access number for your area from the list below: - San Jose/Milpitas (408) area: 525-6800 - RTP (919) area: 392-3330 Dialing the WebEx toll free numbers from within 408 or 919 area codes is no= t enabled (non-Cisco phones). =93 If you dial the toll-free numbers within= the 408 or 919 area codes you will be instructed to hang up and dial the l= ocal access number.=94 Please use the call-back option whenever possible an= d otherwise dial local numbers only. The affected toll free numbers are: (= 866) 432-9903 for the San Jose/Milpitas area and (866) 349-3520 for the RTP= area. ------------------------------------------------------- To join the teleconference only ------------------------------------------------------- 1. Dial into Cisco WebEx (view all Global Access Numbers at http://cisco.com/en/US/about/doing_business/conferencing/index.html 2. Follow the prompts to enter the Meeting Number (listed above) or Access = Code followed by the # sign. San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330 US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117 India: +91.80.4350.1111 Germany: +49.619.6773.9002 Japan: +81.3.5763.9394 China: +86.10.8515.5666 IMPORTANT NOTICE: This WebEx service includes a feature that allows audio a= nd any documents and other materials exchanged or viewed during the session= to be recorded. By joining this session, you automatically consent to such= recordings. If you do not consent to the recording, discuss your concerns = with the meeting host prior to the start of the recording or do not join th= e session. Please note that any such recordings may be subject to discovery= in the event of litigation. http://www.webex.com --_000_489D13FBFA9B3E41812EA89F188F018E1AE1B29Cxmbrcdx04ciscoc_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Discuss how to proceed with applying issues and merging 3633 (and what= ever else). Please be sure to add items to the issue tracker!
 
Updated with Agenda:
 
Folks,<= /div>
Here's an agenda for = upcoming Wednesday, Jan 22nd meeting
8:00 EST (14:00 CET, = 21:00 CST). Bernie sent out meeting invitation in a separate mail.
 <= /div>
1. Confirm that XML f= or 3315 is done.
One outstanding issue= are the cross-references. Bernie said he'll look at that. So this is likel= y to be a very quick item.
 <= /div>
2. Confirm that XML f= or 3633 is done.
Same as above, except= we won't need cross-references as the text will end up being copied over t= o 3315bis, so its references will need to be tweaked anyway.<= /div>
 <= /div>
3. Get over the list = of RFCs we want to merge.
Tomek will send out a= list of candidates. We'll decide for each of them what to do:
a) reference only
b) copy minimal text = (e.g. UUID duid type) and reference the RFC/I-D
c) skip completely
 <= /div>
4. Discuss authorship=
The problem is with t= he number of authors. RFC Editor recommends to not have more than 5 authors= (http://www.rfc-editor.org/policy.html#policy.authlist<= /font>). This is a soft limit, so we can go over if needed, but going for full list = (6 original
3315 authors + 5 = new ones) will likely not be acceptable. Bernie proposed (and Tomek agrees)= to go with the list of DHCPv6bis team members and thank 3315 authors in ac= knowledgement section. We will also want to thank some people that reported errata or issues.
 <= /div>
5. Decide on next ste= ps
Proposal:
 <= /div>
- go over reported is= sues in the tracker. Segregate them into:
  a) obvious/eas= y to do =3D> apply them before merge
  b) widely supp= orted, but harder to do =3D> apply them after merge
  c) contentious= =3D> leave them for discussion on DHC WG
 <= /div>
- apply/close issues = marked as a)
- upload new revision=
- merge=
- upload new revision=
- apply/close issues = makred as b)
- request adoption in= DHC
- discuss issues from= c) group on DHC WG, get consensus on them,
  apply or rejec= t on a per case basis
- WGLC once all issue= s are closed
 <= /div>
6. Go over reported i= ssues in issue tracker and split into groups.
 <= /div>
We'll likely to assig= n owner to each issue. Such owner will be responsible for dealing with the = issue (and lead any discussions that may emerge).
 <= /div>
7. Any other business=
 <= /div>
It seems that the maj= ority of the time spent on the meeting will be about going through the issu= es in issue tracker. Please take a look at them prior to the meeting, if po= ssible.
 <= /div>
Folks, keep in mind t= hat this is very late meeting for Sheng, so please keep the non-essential s= tuff to minimum.
 <= /div>
Bernie & Tomek
 
 
-+-----+-----+-----+= ;-----+-----+-----+-----+-----+-
[Do not add or change anything below this line. The information in thi= s section may be replaced with your meeting details after you click Send.]<= /div>
 
******* DO NOT DELETE OR CHANGE ANY OF THE TEXT BELOW THIS LINE ******= *
 
----------------------------------------------------------------------= -
JOIN USING WebEx
 
Go To:
 
Meeting Password ----- 3315
Meeting Number ----- 204 539 449
 
----------------------------------------------------------------
ALERT =96 PLEASE READ: DO NOT DIAL THE TOLL FREE NUMBERS FROM WITHIN T= HE (408) OR (919) AREA CODES
----------------------------------------------------------------
Please dial the local access number for your area from the list below:=
-  San Jose/Milpitas (408) area:  525-6800
-  RTP (919) area:  392-3330
 
Dialing the WebEx toll free numbers from within 408 or 919 area codes = is not enabled (non-Cisco phones).  =93 If you dial the toll-free numb= ers within the 408 or 919 area codes you will be instructed to hang up and = dial the local access number.=94 Please use the call-back option whenever possible and otherwise dial local numbers onl= y.  The affected toll free numbers are: (866) 432-9903 for the San Jos= e/Milpitas area and (866) 349-3520 for the RTP area.
 
-------------------------------------------------------
To join the teleconference only
-------------------------------------------------------
1. Dial into Cisco WebEx (view all Global Access Numbers at
2. Follow the prompts to enter the Meeting Number (listed above) or Ac= cess Code followed by the # sign.
 
San Jose, CA: +1.408.525.6800  RTP: +1.919.392.3330
 
US/Canada: +1.866.432.9903  United Kingdom: +44.20.8824.0= 117
 
India: +91.80.4350.1111  Germany: +49.619.6773.9002
 
Japan: +81.3.5763.9394  China: +86.10.8515.5666
 
IMPORTANT NOTICE: This WebEx service includes a feature that allows au= dio and any documents and other materials exchanged or viewed during the se= ssion to be recorded. By joining this session, you automatically consent to= such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior= to the start of the recording or do not join the session. Please note that= any such recordings may be subject to discovery in the event of litigation= .
 
     
 
 <= /div> --_000_489D13FBFA9B3E41812EA89F188F018E1AE1B29Cxmbrcdx04ciscoc_ Content-Type: text/calendar; charset="utf-8"; method=PUBLISH Content-Transfer-Encoding: base64 QkVHSU46VkNBTEVOREFSDQpNRVRIT0Q6UFVCTElTSA0KUFJPRElEOk1pY3Jvc29mdCBFeGNoYW5n ZSBTZXJ2ZXIgMjAxMA0KVkVSU0lPTjoyLjANCkJFR0lOOlZUSU1FWk9ORQ0KVFpJRDpFYXN0ZXJu IFN0YW5kYXJkIFRpbWUNCkJFR0lOOlNUQU5EQVJEDQpEVFNUQVJUOjE2MDEwMTAxVDAyMDAwMA0K VFpPRkZTRVRGUk9NOi0wNDAwDQpUWk9GRlNFVFRPOi0wNTAwDQpSUlVMRTpGUkVRPVlFQVJMWTtJ TlRFUlZBTD0xO0JZREFZPTFTVTtCWU1PTlRIPTExDQpFTkQ6U1RBTkRBUkQNCkJFR0lOOkRBWUxJ R0hUDQpEVFNUQVJUOjE2MDEwMTAxVDAyMDAwMA0KVFpPRkZTRVRGUk9NOi0wNTAwDQpUWk9GRlNF VFRPOi0wNDAwDQpSUlVMRTpGUkVRPVlFQVJMWTtJTlRFUlZBTD0xO0JZREFZPTJTVTtCWU1PTlRI PTMNCkVORDpEQVlMSUdIVA0KRU5EOlZUSU1FWk9ORQ0KQkVHSU46VkVWRU5UDQpPUkdBTklaRVI7 Q049QmVybmllIFZvbHogKHZvbHopOk1BSUxUTzp2b2x6QGNpc2NvLmNvbQ0KREVTQ1JJUFRJT047 TEFOR1VBR0U9ZW4tVVM6RGlzY3VzcyBob3cgdG8gcHJvY2VlZCB3aXRoIGFwcGx5aW5nIGlzc3Vl cyBhbmQgDQogbWVyZ2luZyAzNjMzIChhbmQgd2hhdGV2ZXIgZWxzZSkuIFBsZWFzZSBiZSBzdXJl IHRvIGFkZCBpdGVtcyB0byB0aGUgaXNzdWUNCiAgdHJhY2tlciFcblxuVXBkYXRlZCB3aXRoIEFn ZW5kYTpcblxuRm9sa3NcLFxuSGVyZSdzIGFuIGFnZW5kYSBmb3IgdXBjb21pbg0KIGcgV2VkbmVz ZGF5XCwgSmFuIDIybmQgbWVldGluZ1xuODowMCBFU1QgKDE0OjAwIENFVFwsIDIxOjAwIENTVCku IEJlcm5pZSBzDQogZW50IG91dCBtZWV0aW5nIGludml0YXRpb24gaW4gYSBzZXBhcmF0ZSBtYWls LlxuXG4xLiBDb25maXJtIHRoYXQgWE1MIGZvciANCiAzMzE1IGlzIGRvbmUuXG5PbmUgb3V0c3Rh bmRpbmcgaXNzdWUgYXJlIHRoZSBjcm9zcy1yZWZlcmVuY2VzLiBCZXJuaWUgc2FpZA0KICBoZSds bCBsb29rIGF0IHRoYXQuIFNvIHRoaXMgaXMgbGlrZWx5IHRvIGJlIGEgdmVyeSBxdWljayBpdGVt LlxuXG4yLiBDb25mDQogaXJtIHRoYXQgWE1MIGZvciAzNjMzIGlzIGRvbmUuXG5TYW1lIGFzIGFi b3ZlXCwgZXhjZXB0IHdlIHdvbid0IG5lZWQgY3Jvc3MNCiAtcmVmZXJlbmNlcyBhcyB0aGUgdGV4 dCB3aWxsIGVuZCB1cCBiZWluZyBjb3BpZWQgb3ZlciB0byAzMzE1YmlzXCwgc28gaXRzIA0KIHJl ZmVyZW5jZXMgd2lsbCBuZWVkIHRvIGJlIHR3ZWFrZWQgYW55d2F5LlxuXG4zLiBHZXQgb3ZlciB0 aGUgbGlzdCBvZiBSRkNzDQogIHdlIHdhbnQgdG8gbWVyZ2UuXG5Ub21layB3aWxsIHNlbmQgb3V0 IGEgbGlzdCBvZiBjYW5kaWRhdGVzLiBXZSdsbCBkZWNpZGUNCiAgZm9yIGVhY2ggb2YgdGhlbSB3 aGF0IHRvIGRvOlxuYSkgcmVmZXJlbmNlIG9ubHlcbmIpIGNvcHkgbWluaW1hbCB0ZXh0IChlLg0K IGcuIFVVSUQgZHVpZCB0eXBlKSBhbmQgcmVmZXJlbmNlIHRoZSBSRkMvSS1EXG5jKSBza2lwIGNv bXBsZXRlbHlcblxuNC4gRGlzDQogY3VzcyBhdXRob3JzaGlwXG5UaGUgcHJvYmxlbSBpcyB3aXRo IHRoZSBudW1iZXIgb2YgYXV0aG9ycy4gUkZDIEVkaXRvciByZWMNCiBvbW1lbmRzIHRvIG5vdCBo YXZlIG1vcmUgdGhhbiA1IGF1dGhvcnMgKGh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcvcG9saWN5 Lg0KIGh0bWwjcG9saWN5LmF1dGhsaXN0KS4gVGhpcyBpcyBhIHNvZnQgbGltaXRcLCBzbyB3ZSBj YW4gZ28gb3ZlciBpZiBuZWVkZWRcDQogLCBidXQgZ29pbmcgZm9yIGZ1bGwgbGlzdCAoNiBvcmln aW5hbFxuMzMxNSBhdXRob3JzICsgNSBuZXcgb25lcykgd2lsbCBsaWsNCiBlbHkgbm90IGJlIGFj Y2VwdGFibGUuIEJlcm5pZSBwcm9wb3NlZCAoYW5kIFRvbWVrIGFncmVlcykgdG8gZ28gd2l0aCB0 aGUgbA0KIGlzdCBvZiBESENQdjZiaXMgdGVhbSBtZW1iZXJzIGFuZCB0aGFuayAzMzE1IGF1dGhv cnMgaW4gYWNrbm93bGVkZ2VtZW50IHNlDQogY3Rpb24uIFdlIHdpbGwgYWxzbyB3YW50IHRvIHRo YW5rIHNvbWUgcGVvcGxlIHRoYXQgcmVwb3J0ZWQgZXJyYXRhIG9yIGlzc3UNCiBlcy5cblxuNS4g RGVjaWRlIG9uIG5leHQgc3RlcHNcblByb3Bvc2FsOlxuXG4tIGdvIG92ZXIgcmVwb3J0ZWQgaXNz dWVzIGluIA0KIHRoZSB0cmFja2VyLiBTZWdyZWdhdGUgdGhlbSBpbnRvOlxuICBhKSBvYnZpb3Vz L2Vhc3kgdG8gZG8gPT4gYXBwbHkgdGhlbSBiDQogZWZvcmUgbWVyZ2VcbiAgYikgd2lkZWx5IHN1 cHBvcnRlZFwsIGJ1dCBoYXJkZXIgdG8gZG8gPT4gYXBwbHkgdGhlbSBhZnRlciANCiBtZXJnZVxu ICBjKSBjb250ZW50aW91cyA9PiBsZWF2ZSB0aGVtIGZvciBkaXNjdXNzaW9uIG9uIERIQyBXR1xu XG4tIGFwcGx5Lw0KIGNsb3NlIGlzc3VlcyBtYXJrZWQgYXMgYSlcbi0gdXBsb2FkIG5ldyByZXZp c2lvblxuLSBtZXJnZVxuLSB1cGxvYWQgbmV3IHJlDQogdmlzaW9uXG4tIGFwcGx5L2Nsb3NlIGlz c3VlcyBtYWtyZWQgYXMgYilcbi0gcmVxdWVzdCBhZG9wdGlvbiBpbiBESENcbi0gZGkNCiBzY3Vz cyBpc3N1ZXMgZnJvbSBjKSBncm91cCBvbiBESEMgV0dcLCBnZXQgY29uc2Vuc3VzIG9uIHRoZW1c LFxuICBhcHBseSBvcg0KICByZWplY3Qgb24gYSBwZXIgY2FzZSBiYXNpc1xuLSBXR0xDIG9uY2Ug YWxsIGlzc3VlcyBhcmUgY2xvc2VkXG5cbjYuIEdvIG92DQogZXIgcmVwb3J0ZWQgaXNzdWVzIGlu IGlzc3VlIHRyYWNrZXIgYW5kIHNwbGl0IGludG8gZ3JvdXBzLlxuXG5XZSdsbCBsaWtlbHkNCiAg dG8gYXNzaWduIG93bmVyIHRvIGVhY2ggaXNzdWUuIFN1Y2ggb3duZXIgd2lsbCBiZSByZXNwb25z aWJsZSBmb3IgZGVhbGluZw0KICB3aXRoIHRoZSBpc3N1ZSAoYW5kIGxlYWQgYW55IGRpc2N1c3Np b25zIHRoYXQgbWF5IGVtZXJnZSkuXG5cbjcuIEFueSBvdGhlDQogciBidXNpbmVzc1xuXG5JdCBz ZWVtcyB0aGF0IHRoZSBtYWpvcml0eSBvZiB0aGUgdGltZSBzcGVudCBvbiB0aGUgbWVldGluZyAN CiB3aWxsIGJlIGFib3V0IGdvaW5nIHRocm91Z2ggdGhlIGlzc3VlcyBpbiBpc3N1ZSB0cmFja2Vy LiBQbGVhc2UgdGFrZSBhIGxvbw0KIGsgYXQgdGhlbSBwcmlvciB0byB0aGUgbWVldGluZ1wsIGlm IHBvc3NpYmxlLlxuXG5Gb2xrc1wsIGtlZXAgaW4gbWluZCB0aGF0DQogIHRoaXMgaXMgdmVyeSBs YXRlIG1lZXRpbmcgZm9yIFNoZW5nXCwgc28gcGxlYXNlIGtlZXAgdGhlIG5vbi1lc3NlbnRpYWwg c3QNCiB1ZmYgdG8gbWluaW11bS5cblxuQmVybmllICYgVG9tZWtcblxuXG4tKy0tLS0tKy0tLS0t Ky0tLS0tKy0tLS0tKy0tLS0tKy0tLQ0KIC0tKy0tLS0tKy0tLS0tKy1cbltEbyBub3QgYWRkIG9y IGNoYW5nZSBhbnl0aGluZyBiZWxvdyB0aGlzIGxpbmUuIFRoZSBpbmZvDQogcm1hdGlvbiBpbiB0 aGlzIHNlY3Rpb24gbWF5IGJlIHJlcGxhY2VkIHdpdGggeW91ciBtZWV0aW5nIGRldGFpbHMgYWZ0 ZXIgeW8NCiB1IGNsaWNrIFNlbmQuXVxuXG4qKioqKioqIERPIE5PVCBERUxFVEUgT1IgQ0hBTkdF IEFOWSBPRiBUSEUgVEVYVCBCRUxPVyBUSA0KIElTIExJTkUgKioqKioqKlxuXG4tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQogLS0tLS0tLS0t LS0tLS0tLVxuSk9JTiBVU0lORyBXZWJFeFxuXG5HbyBUbzpcbmh0dHBzOi8vY2lzY28ud2ViZXgu Y29tL2Npc2MNCiBvL2oucGhwP0o9MjA0NTM5NDQ5JlBXPU5OekpsWXpFM01UazNcblxuTWVldGlu ZyBQYXNzd29yZCAtLS0tLSAzMzE1XG5NZWV0aQ0KIG5nIE51bWJlciAtLS0tLSAyMDQgNTM5IDQ0 OVxuXG4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQogLS0tLS0t LS0tLS0tLS0tLS0tLS0tXG5BTEVSVCDigJMgUExFQVNFIFJFQUQ6IERPIE5PVCBESUFMIFRIRSBU T0xMIEZSRUUgTlUNCiBNQkVSUyBGUk9NIFdJVEhJTiBUSEUgKDQwOCkgT1IgKDkxOSkgQVJFQSBD T0RFU1xuLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLVxuUGxlYXNlIGRpYWwgdGhlIGxvY2FsIGFjY2VzcyBudW1iDQogZXIg Zm9yIHlvdXIgYXJlYSBmcm9tIHRoZSBsaXN0IGJlbG93OlxuLSAgU2FuIEpvc2UvTWlscGl0YXMg KDQwOCkgYXJlYTogIDUNCiAyNS02ODAwXG4tICBSVFAgKDkxOSkgYXJlYTogIDM5Mi0zMzMwXG5c bkRpYWxpbmcgdGhlIFdlYkV4IHRvbGwgZnJlZSBudW1iZQ0KIHJzIGZyb20gd2l0aGluIDQwOCBv ciA5MTkgYXJlYSBjb2RlcyBpcyBub3QgZW5hYmxlZCAobm9uLUNpc2NvIHBob25lcykuICANCiDi gJwgSWYgeW91IGRpYWwgdGhlIHRvbGwtZnJlZSBudW1iZXJzIHdpdGhpbiB0aGUgNDA4IG9yIDkx OSBhcmVhIGNvZGVzIHlvdQ0KICB3aWxsIGJlIGluc3RydWN0ZWQgdG8gaGFuZyB1cCBhbmQgZGlh bCB0aGUgbG9jYWwgYWNjZXNzIG51bWJlci7igJ0gUGxlYXNlDQogIHVzZSB0aGUgY2FsbC1iYWNr IG9wdGlvbiB3aGVuZXZlciBwb3NzaWJsZSBhbmQgb3RoZXJ3aXNlIGRpYWwgbG9jYWwgbnVtYmUN CiBycyBvbmx5LiAgVGhlIGFmZmVjdGVkIHRvbGwgZnJlZSBudW1iZXJzIGFyZTogKDg2NikgNDMy LTk5MDMgZm9yIHRoZSBTYW4gSg0KIG9zZS9NaWxwaXRhcyBhcmVhIGFuZCAoODY2KSAzNDktMzUy MCBmb3IgdGhlIFJUUCBhcmVhLlxuXG4tLS0tLS0tLS0tLS0tLS0tDQogLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tXG5UbyBqb2luIHRoZSB0ZWxlY29uZmVyZW5jZSBvbmx5 XG4NCiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tXG4xLiBEaWFsIGludG8gQ2lzYw0KIG8gV2ViRXggKHZpZXcgYWxsIEdsb2JhbCBBY2Nlc3Mg TnVtYmVycyBhdFxuaHR0cDovL2Npc2NvLmNvbS9lbi9VUy9hYm91dC9kDQogb2luZ19idXNpbmVz cy9jb25mZXJlbmNpbmcvaW5kZXguaHRtbFxuMi4gRm9sbG93IHRoZSBwcm9tcHRzIHRvIGVudGVy IHRoZSANCiBNZWV0aW5nIE51bWJlciAobGlzdGVkIGFib3ZlKSBvciBBY2Nlc3MgQ29kZSBmb2xs b3dlZCBieSB0aGUgIyBzaWduLlxuXG5TYQ0KIG4gSm9zZVwsIENBOiArMS40MDguNTI1LjY4MDAg IFJUUDogKzEuOTE5LjM5Mi4zMzMwXG5cblVTL0NhbmFkYTogKzEuODY2LjQzDQogMi45OTAzICBV bml0ZWQgS2luZ2RvbTogKzQ0LjIwLjg4MjQuMDExN1xuXG5JbmRpYTogKzkxLjgwLjQzNTAuMTEx MSAgR2VybWENCiBueTogKzQ5LjYxOS42NzczLjkwMDJcblxuSmFwYW46ICs4MS4zLjU3NjMuOTM5 NCAgQ2hpbmE6ICs4Ni4xMC44NTE1LjU2NjZcbg0KIFxuSU1QT1JUQU5UIE5PVElDRTogVGhpcyBX ZWJFeCBzZXJ2aWNlIGluY2x1ZGVzIGEgZmVhdHVyZSB0aGF0IGFsbG93cyBhdWRpDQogbyBhbmQg YW55IGRvY3VtZW50cyBhbmQgb3RoZXIgbWF0ZXJpYWxzIGV4Y2hhbmdlZCBvciB2aWV3ZWQgZHVy aW5nIHRoZSBzZXMNCiBzaW9uIHRvIGJlIHJlY29yZGVkLiBCeSBqb2luaW5nIHRoaXMgc2Vzc2lv blwsIHlvdSBhdXRvbWF0aWNhbGx5IGNvbnNlbnQgdA0KIG8gc3VjaCByZWNvcmRpbmdzLiBJZiB5 b3UgZG8gbm90IGNvbnNlbnQgdG8gdGhlIHJlY29yZGluZ1wsIGRpc2N1c3MgeW91ciBjDQogb25j ZXJucyB3aXRoIHRoZSBtZWV0aW5nIGhvc3QgcHJpb3IgdG8gdGhlIHN0YXJ0IG9mIHRoZSByZWNv cmRpbmcgb3IgZG8gbm8NCiB0IGpvaW4gdGhlIHNlc3Npb24uIFBsZWFzZSBub3RlIHRoYXQgYW55 IHN1Y2ggcmVjb3JkaW5ncyBtYXkgYmUgc3ViamVjdCB0bw0KICBkaXNjb3ZlcnkgaW4gdGhlIGV2 ZW50IG9mIGxpdGlnYXRpb24uXG5cbmh0dHA6Ly93d3cud2ViZXguY29tXG5cblxuXG4NClNVTU1B Ulk7TEFOR1VBR0U9ZW4tVVM6REhDUHY2YmlzIFRlYW0gTWVldGluZyAtIE5leHQgU3RlcHMNCkRU U1RBUlQ7VFpJRD1FYXN0ZXJuIFN0YW5kYXJkIFRpbWU6MjAxNDAxMjJUMDgwMDAwDQpEVEVORDtU WklEPUVhc3Rlcm4gU3RhbmRhcmQgVGltZToyMDE0MDEyMlQwOTAwMDANClVJRDowNDAwMDAwMDgy MDBFMDAwNzRDNUI3MTAxQTgyRTAwODAwMDAwMDAwQTA1MzFGNEM2MDEwQ0YwMTAwMDAwMDAwMDAw MDAwMA0KIDAxMDAwMDAwMDhBNTZERjFGRDk0NzQzNDc5RDMxRjFCMjUxMzlGQTIxDQpDTEFTUzpQ VUJMSUMNClBSSU9SSVRZOjUNCkRUU1RBTVA6MjAxNDAxMjBUMTg0NzQwWg0KVFJBTlNQOk9QQVFV RQ0KU1RBVFVTOkNPTkZJUk1FRA0KU0VRVUVOQ0U6MQ0KTE9DQVRJT047TEFOR1VBR0U9ZW4tVVM6 V2ViRXgNClgtTUlDUk9TT0ZULUNETy1BUFBULVNFUVVFTkNFOjENClgtTUlDUk9TT0ZULUNETy1P V05FUkFQUFRJRDotMTIzNjQ2MTYwMg0KWC1NSUNST1NPRlQtQ0RPLUJVU1lTVEFUVVM6QlVTWQ0K WC1NSUNST1NPRlQtQ0RPLUlOVEVOREVEU1RBVFVTOkJVU1kNClgtTUlDUk9TT0ZULUNETy1BTExE QVlFVkVOVDpGQUxTRQ0KWC1NSUNST1NPRlQtQ0RPLUlNUE9SVEFOQ0U6MQ0KWC1NSUNST1NPRlQt Q0RPLUlOU1RUWVBFOjANClgtTUlDUk9TT0ZULURJU0FMTE9XLUNPVU5URVI6RkFMU0UNCkJFR0lO OlZBTEFSTQ0KQUNUSU9OOkRJU1BMQVkNCkRFU0NSSVBUSU9OOlJFTUlOREVSDQpUUklHR0VSO1JF TEFURUQ9U1RBUlQ6LVBUMTVNDQpFTkQ6VkFMQVJNDQpFTkQ6VkVWRU5UDQpFTkQ6VkNBTEVOREFS DQo= --_000_489D13FBFA9B3E41812EA89F188F018E1AE1B29Cxmbrcdx04ciscoc_-- --_004_489D13FBFA9B3E41812EA89F188F018E1AE2D20Axmbrcdx04ciscoc_-- From volz@cisco.com Tue Jan 21 08:23:45 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48AC21A0373 for ; Tue, 21 Jan 2014 08:23:45 -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 9zY97OinEK0v for ; Tue, 21 Jan 2014 08:23:44 -0800 (PST) Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id DE7221A0385 for ; Tue, 21 Jan 2014 08:23:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1385; q=dns/txt; s=iport; t=1390321424; x=1391531024; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=Kl0C4tCf1CCmh5OmQix0TO67NfkMBfF6DkLdNsRnYLo=; b=NcTIU5OwXVp0kOozkqHO9EWn3RRFrTDwh86yypXYI294T2A0foNYvtmv btkZS7xZORQuUF6LviXPjd6q1FhuE81u/I8nuLnW5Wuk1GMnyZb70WUzG Do/8s9Cc2GsTKop+jmqWOGLnw8NQrATizTj65ltU10kNJlnr+Mkjm7IlM 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhYFAO+d3lKtJXG//2dsb2JhbABZgws4VrttgRMWdIIlAQEBBDpLBAIBCBEEAQELFAkHMhQHAQEFAwIEEwgMh3ENw34Xjh0RAR84BoMegRQEmVSQZoMtgXE5 X-IronPort-AV: E=Sophos;i="4.95,696,1384300800"; d="scan'208";a="14404923" Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by alln-iport-8.cisco.com with ESMTP; 21 Jan 2014 16:23:43 +0000 Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0LGNhT5001199 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 21 Jan 2014 16:23:43 GMT Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0123.003; Tue, 21 Jan 2014 10:23:43 -0600 From: "Bernie Volz (volz)" To: "dhcpv6bis@ietf.org" Thread-Topic: Web-based email list archive search and browsing tool ready for use Thread-Index: AQHPFsRxJT4C5zZ1qkSgo/I3Q9fsXJqPXJWA Date: Tue, 21 Jan 2014 16:23:42 +0000 Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE2D252@xmb-rcd-x04.cisco.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [161.44.65.114] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [Dhcpv6bis] FW: Web-based email list archive search and browsing tool ready for use X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 16:23:45 -0000 FYI - See below ... could be useful for searching email archives for issues= . -----Original Message----- From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of IETF Chair Sent: Tuesday, January 21, 2014 11:18 AM To: Working Group Chairs Cc: Robert Sparks Subject: Web-based email list archive search and browsing tool ready for us= e Chairs: The tool realizing the requirements we developed in RFC 6778 is ready for y= our use. We are announcing it to the working group chairs first to bring th= e load onto this new service incrementally. We will send an announcement to= the entire community later this week. You'll find the service at https://mailarchive.ietf.org/ If you choose to log in, use your datatracker credentials. If you encounter problems or have suggestions for future improvements, plea= se file a report using http://trac.tools.ietf.org/tools/ietfdb/newticket=20 If you find spam, please send a request to remove it including a link to th= e message to action@ietf.org. We are still working towards providing IMAP access to the archives. That is= not part of the tool at this time. The old archives will continue to recei= ve new messages and will be available in their current locations until furt= her notice. Early testers have reported this tool to be very useful. I hope you also fi= nd it to be so. Jari From mcr@sandelman.ca Tue Jan 21 10:20:10 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 264D11A0157 for ; Tue, 21 Jan 2014 10:20:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.019 X-Spam-Level: * X-Spam-Status: No, score=1.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no 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 bu_Mw5SMfjUG for ; Tue, 21 Jan 2014 10:20:08 -0800 (PST) Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id F23691A0135 for ; Tue, 21 Jan 2014 10:20:07 -0800 (PST) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D4CE220049; Tue, 21 Jan 2014 14:36:12 -0500 (EST) Received: by sandelman.ca (Postfix, from userid 179) id F085164647; Tue, 21 Jan 2014 13:20:05 -0500 (EST) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id DDBE963AB2; Tue, 21 Jan 2014 13:20:05 -0500 (EST) From: Michael Richardson To: dhcpv6bis@ietf.org In-Reply-To: <52DD6E41.7080708@gmail.com> References: <489D13FBFA9B3E41812EA89F188F018E1AE2AB2E@xmb-rcd-x04.cisco.com> <52DD6E41.7080708@gmail.com> X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Sender: mcr@sandelman.ca Cc: Tomek Mrugalski Subject: Re: [Dhcpv6bis] Agenda for dhcpv6bis meeting on 2014-01-22 X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 18:20:10 -0000 --=-=-= Tomek Mrugalski wrote: > 4. Discuss authorship > The problem is with the number of authors. RFC Editor recommends to not > have more than 5 authors > (http://www.rfc-editor.org/policy.html#policy.authlist). This is a soft > limit, so we can go over if needed, but going for full list (6 original > 3315 authors + 5 new ones) will likely not be acceptable. Bernie > proposed (and Tomek agrees) to go with the list of DHCPv6bis team > members and thank 3315 authors in acknowledgement section. We will also > want to thank some people that reported errata or issues. Let's establish a subsection clearly for 3315. Operationally, we need to have at least one name on the official author list who can easily post new revisions, and I think that right now, that's Bernie Volz (probably has to update his email tho) > 5. Decide on next steps > Proposal: > - go over reported issues in the tracker. Segregate them into: > a) obvious/easy to do => apply them before merge > b) widely supported, but harder to do => apply them after merge > c) contentious => leave them for discussion on DHC WG We are doing this as a group? shared screen? > 7. Any other business > It seems that the majority of the time spent on the meeting will be > about going through the issues in issue tracker. Please take a look at > them prior to the meeting, if possible. I think that I've missed/forgotten the link to the issue tracker, I find nothing at: http://trac.tools.ietf.org/wg/dhc/trac/report/1 once we post the -00 as a WG document, we'll have a category for isssues, but where are the issues being kept right now? Maybe it was in github? Nope. -- Michael Richardson , Sandelman Software Works --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQCVAwUBUt66U4qHRg3pndX9AQJeOQQAn9vilJGNTfxEDmttQl0uylbL2ZSN1mqH /GYTbkFNQ+xQsEbKDJuPEX9Y7QaSCh4bE56Q3W8NOxK8yBfGsivlmfRIvbBfMfXq a4ATUBYCfWga7eB844IS0WtHl7TZroYo5STUYe7Xzzk1j9h1YUqPnC1rBoIu3Otx 1EGwvvD6FmA= =RrZi -----END PGP SIGNATURE----- --=-=-=-- From volz@cisco.com Tue Jan 21 10:23:44 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 558221A0191 for ; Tue, 21 Jan 2014 10:23:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.036 X-Spam-Level: X-Spam-Status: No, score=-15.036 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, 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 XwDe8r8HGQPQ for ; Tue, 21 Jan 2014 10:23:42 -0800 (PST) Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 856891A0135 for ; Tue, 21 Jan 2014 10:23:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2361; q=dns/txt; s=iport; t=1390328622; x=1391538222; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=MxodOYZw4uT9Ua7qlhnyyGP1E5Yj8dMje3OerT+AmDY=; b=lztORm1vAG4OeI5WGdevBW1Pjl0ye5VeWjcC+Sqal5P41NnRcFM7Aa2p N8zK8PDzyrfavxsvskuojphF8cvWJprFCX3Kt4Hf/hdAjQ0c3SbUtNIYu RlmrjPlwpLZApjPyeJDPyyzlSggZgk6RWY8dEbc3RlyQhxWDHELPuGmJA U=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhYFAE+63lKtJXHA/2dsb2JhbABZgws4VrttgRUWdIIlAQEBAwE6PwwEAgEIEQQBAQEKFAkHIREUCQgCBAENBQiHaQMJCA29Xw2FVheMa4EyCwYBHzEHBoMegRQEljaDHosrhTuDLYFpCBci X-IronPort-AV: E=Sophos;i="4.95,696,1384300800"; d="scan'208";a="298728272" Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-5.cisco.com with ESMTP; 21 Jan 2014 18:23:42 +0000 Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id s0LINgss010800 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Jan 2014 18:23:42 GMT Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0123.003; Tue, 21 Jan 2014 12:23:42 -0600 From: "Bernie Volz (volz)" To: Michael Richardson , "dhcpv6bis@ietf.org" Thread-Topic: [Dhcpv6bis] Agenda for dhcpv6bis meeting on 2014-01-22 Thread-Index: AQHPFtV7z6Z88kfnrkaXRevkOwz3zJqPfaHg Date: Tue, 21 Jan 2014 18:23:41 +0000 Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE2D5DF@xmb-rcd-x04.cisco.com> References: <489D13FBFA9B3E41812EA89F188F018E1AE2AB2E@xmb-rcd-x04.cisco.com> <52DD6E41.7080708@gmail.com> <4625.1390328405@sandelman.ca> In-Reply-To: <4625.1390328405@sandelman.ca> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [161.44.65.114] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Tomek Mrugalski Subject: Re: [Dhcpv6bis] Agenda for dhcpv6bis meeting on 2014-01-22 X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 18:23:44 -0000 That email address is a valid one for me. Though I do plan to change it onc= e we update the author information. Issues are at http://trac.tools.ietf.org/group/dhcpv6bis/report/1. - Bernie -----Original Message----- From: Dhcpv6bis [mailto:dhcpv6bis-bounces@ietf.org] On Behalf Of Michael Ri= chardson Sent: Tuesday, January 21, 2014 1:20 PM To: dhcpv6bis@ietf.org Cc: Tomek Mrugalski Subject: Re: [Dhcpv6bis] Agenda for dhcpv6bis meeting on 2014-01-22 Tomek Mrugalski wrote: > 4. Discuss authorship > The problem is with the number of authors. RFC Editor recommends to n= ot > have more than 5 authors > (http://www.rfc-editor.org/policy.html#policy.authlist). This is a so= ft > limit, so we can go over if needed, but going for full list (6 origin= al > 3315 authors + 5 new ones) will likely not be acceptable. Bernie > proposed (and Tomek agrees) to go with the list of DHCPv6bis team > members and thank 3315 authors in acknowledgement section. We will al= so > want to thank some people that reported errata or issues. Let's establish a subsection clearly for 3315. Operationally, we need to have at least one name on the official author lis= t who can easily post new revisions, and I think that right now, that's Ber= nie Volz (probably has to update his email tho) > 5. Decide on next steps > Proposal: > - go over reported issues in the tracker. Segregate them into: > a) obvious/easy to do =3D> apply them before merge > b) widely supported, but harder to do =3D> apply them after merge > c) contentious =3D> leave them for discussion on DHC WG We are doing this as a group? shared screen? > 7. Any other business > It seems that the majority of the time spent on the meeting will be > about going through the issues in issue tracker. Please take a look a= t > them prior to the meeting, if possible. I think that I've missed/forgotten the link to the issue tracker, I find no= thing at: http://trac.tools.ietf.org/wg/dhc/trac/report/1 once we post the -00 as a WG document, we'll have a category for isssues, b= ut where are the issues being kept right now? Maybe it was in github? Nope. -- Michael Richardson , Sandelman Software Works From tomasz.mrugalski@gmail.com Wed Jan 22 04:58:31 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB8381A0117 for ; Wed, 22 Jan 2014 04:58:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 3sX2RtyFM3DA for ; Wed, 22 Jan 2014 04:58:30 -0800 (PST) Received: from mail-ee0-x236.google.com (mail-ee0-x236.google.com [IPv6:2a00:1450:4013:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD191A00C6 for ; Wed, 22 Jan 2014 04:58:30 -0800 (PST) Received: by mail-ee0-f54.google.com with SMTP id e53so4123175eek.27 for ; Wed, 22 Jan 2014 04:58:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=6GSk7OOALHVkaG3JcDGS6/xSkUvx8NPs8J1yGZ3Kwwg=; b=qicok4+Ml122Sly3Rg4xxVF80OP2HUnskjlmiubqJhDoHCJHqv4TE0zhwkN2P37COu +PxkqoQ+3CVbYOzYE8VDmFOpgDEpuKjbd1g6LyhnI4qLrRITi4/4Z8gnS2K6ift16VsJ wJI7wQRYTSilRkY6DeVnsi58xR8tHrQ77mtV1hdiwnHNguUW554RtHhTdbZDztuRaGQ+ QG6ZZvX3HFlaD8rydVYq2fkfg+V1NHLvy1+8jQxWiQ0NLhwZnJ3pO1ywnFW1f5mXrTU8 qYAJnrZ7aZAzBocYns7iuVEulMz1F0Bqs/T9nOl4b4BcWrOmvyYQ3lo7lQDVPcKuEtHQ Q3iQ== X-Received: by 10.14.251.68 with SMTP id a44mr1439553ees.64.1390395509722; Wed, 22 Jan 2014 04:58:29 -0800 (PST) Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id m47sm26862284eey.7.2014.01.22.04.58.26 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Jan 2014 04:58:28 -0800 (PST) Message-ID: <52DFC06A.7070902@gmail.com> Date: Wed, 22 Jan 2014 13:58:18 +0100 From: Tomek Mrugalski User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: dhcpv6bis@ietf.org X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Dhcpv6bis] RFCs/drafts possibly considered for inclusion X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 12:58:32 -0000 Sorry for sending this list so late. Here's a list of RFCs/drafts that we can consider for the 3315bis work: RFC3633 - That's obvious. We already decided to merge it in. Included here for completeness. RFC7083 - Add a text that SOL_MAX_RT and INF_MAX_RT should be processed by clients even if status code indicates failure. RFC6977 - Triggered reconfigure. Make explicit the currently implicit assumption that the relays do not modify client's messages RFC3736 - stateless DHCPV6 RFC6355 - DUID-UUID Probably just add UUID type 4 to the list and add reference RFC6644 - rebind in reconfigure Allow reconfigure to rigger REBIND. RFC6422 - relay supplied options ... stateful-issues - ... unknown-msg - uknown messages being handled by relays Let's discuss this on the meeting today. Tomek From volz@cisco.com Wed Jan 22 06:48:22 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 800B91A0438 for ; Wed, 22 Jan 2014 06:48:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -12.036 X-Spam-Level: X-Spam-Status: No, score=-12.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_INVITATION=-2, 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 pJkhLIR6IUOy for ; Wed, 22 Jan 2014 06:48:20 -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 917261A043C for ; Wed, 22 Jan 2014 06:48:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4309; q=dns/txt; s=iport; t=1390402098; x=1391611698; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=fzm7izV5mu+IDfKGyhYezWNWtZ76elFjIhtrLxVFPsQ=; b=PsjIx6h7jDXMUv3SqUbgEGew+UCaFkQcrqkv1qWyJf4JTFXEd+A97zQ6 0WAlQrRv1/nzq4GDI4LcuZvsjJZ37m10HsVQi/aDUYQGp7+HCYzlfkE4d /YS8XLV2rihODjnsmpRTfxwW1mGlmI6e0oAnexaFJ8IW9rLpvIGNWzPE8 o=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhwFAHfZ31KtJXG//2dsb2JhbABagws4VrsPT4ERFnSCJQEBAQQBAQE3NBcEAgEIEQQBAQEKFAkHJwsUCQgCBAESCId9DcIzF44lBgEBHjgGgx6BFASqOoMtgWkIFyI X-IronPort-AV: E=Sophos;i="4.95,700,1384300800"; d="scan'208";a="14675540" Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by alln-iport-2.cisco.com with ESMTP; 22 Jan 2014 14:48:15 +0000 Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0MEmFc2011099 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Wed, 22 Jan 2014 14:48:15 GMT Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0123.003; Wed, 22 Jan 2014 08:48:14 -0600 From: "Bernie Volz (volz)" To: "Andrew Yourtchenko (ayourtch)" , "dhcpv6bis@ietf.org" Thread-Topic: [Dhcpv6bis] Agenda for dhcpv6bis meeting on 2014-01-22 Thread-Index: AQHPFg+BRBK18Eknw0+r8g4RdL27QJqOWRiAgAJ7hNA= Date: Wed, 22 Jan 2014 14:48:14 +0000 Message-ID: <489D13FBFA9B3E41812EA89F188F018E1AE2EB4C@xmb-rcd-x04.cisco.com> References: <489D13FBFA9B3E41812EA89F188F018E1AE2AB2E@xmb-rcd-x04.cisco.com> <52DD6E41.7080708@gmail.com> <52DD6FAB.3090609@gmail.com> In-Reply-To: <52DD6FAB.3090609@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.86.242.170] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [Dhcpv6bis] Agenda for dhcpv6bis meeting on 2014-01-22 X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 14:48:22 -0000 Andrew: We assigned you to work with Michael on X: "X. Come up with the merge 3633/3315 strategy. This looks like a too big task for a single person, so we'll probably try t= o split this work among two volunteers. Haven't given much thought about ho= w to do this, but each person being responsible for moving roughly a half o= f the 3633 sections seems like a good idea." This is to PLAN the merge (what terminology to use, i.e. Requesting Router = =3D DHCPv6 Client for PD) and what will need to be updated in RFC 3315 (new= sections to add, sections to update, etc.). Note also that stateful issues= draft changes some PD related items so be mindful of this (though those ar= e not yet 'approved'). If you are not comfortable with this, let us know and we can assign someone= else. - Bernie -----Original Message----- From: Dhcpv6bis [mailto:dhcpv6bis-bounces@ietf.org] On Behalf Of Tomek Mrug= alski Sent: Monday, January 20, 2014 1:49 PM To: dhcpv6bis@ietf.org Subject: Re: [Dhcpv6bis] Agenda for dhcpv6bis meeting on 2014-01-22 Oops, Forgot about one extra item: X. Come up with the merge 3633/3315 strategy. This looks like a too big task for a single person, so we'll probably try t= o split this work among two volunteers. Haven't given much thought about ho= w to do this, but each person being responsible for moving roughly a half o= f the 3633 sections seems like a good idea. Tomek On 20.01.2014 19:43, Tomek Mrugalski wrote: > Folks, > Here's an agenda for upcoming Wednesday, Jan 22nd meeting > 8:00 EST (14:00 CET, 21:00 CST). Bernie sent out meeting invitation in=20 > a separate mail. >=20 > 1. Confirm that XML for 3315 is done. > One outstanding issue are the cross-references. Bernie said he'll look=20 > at that. So this is likely to be a very quick item. >=20 > 2. Confirm that XML for 3633 is done. > Same as above, except we won't need cross-references as the text will=20 > end up being copied over to 3315bis, so its references will need to be=20 > tweaked anyway. >=20 > 3. Get over the list of RFCs we want to merge. > Tomek will send out a list of candidates. We'll decide for each of=20 > them what to do: > a) reference only > b) copy minimal text (e.g. UUID duid type) and reference the RFC/I-D > c) skip completely >=20 > 4. Discuss authorship > The problem is with the number of authors. RFC Editor recommends to=20 > not have more than 5 authors=20 > (http://www.rfc-editor.org/policy.html#policy.authlist). This is a=20 > soft limit, so we can go over if needed, but going for full list (6=20 > original > 3315 authors + 5 new ones) will likely not be acceptable. Bernie=20 > proposed (and Tomek agrees) to go with the list of DHCPv6bis team=20 > members and thank 3315 authors in acknowledgement section. We will=20 > also want to thank some people that reported errata or issues. >=20 > 5. Decide on next steps > Proposal: >=20 > - go over reported issues in the tracker. Segregate them into: > a) obvious/easy to do =3D> apply them before merge > b) widely supported, but harder to do =3D> apply them after merge > c) contentious =3D> leave them for discussion on DHC WG >=20 > - apply/close issues marked as a) > - upload new revision > - merge > - upload new revision > - apply/close issues makred as b) > - request adoption in DHC > - discuss issues from c) group on DHC WG, get consensus on them, > apply or reject on a per case basis > - WGLC once all issues are closed >=20 > 6. Go over reported issues in issue tracker and split into groups. >=20 > We'll likely to assign owner to each issue. Such owner will be=20 > responsible for dealing with the issue (and lead any discussions that=20 > may emerge). >=20 > 7. Any other business >=20 > It seems that the majority of the time spent on the meeting will be=20 > about going through the issues in issue tracker. Please take a look at=20 > them prior to the meeting, if possible. >=20 > Folks, keep in mind that this is very late meeting for Sheng, so=20 > please keep the non-essential stuff to minimum. >=20 > Bernie & Tomek >=20 _______________________________________________ Dhcpv6bis mailing list Dhcpv6bis@ietf.org https://www.ietf.org/mailman/listinfo/dhcpv6bis From tomasz.mrugalski@gmail.com Wed Jan 22 07:53:16 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7E371A02D9 for ; Wed, 22 Jan 2014 07:53:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 ppLfKsJ-AZyK for ; Wed, 22 Jan 2014 07:53:14 -0800 (PST) Received: from mail-ea0-x22b.google.com (mail-ea0-x22b.google.com [IPv6:2a00:1450:4013:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 35CB91A02D5 for ; Wed, 22 Jan 2014 07:53:14 -0800 (PST) Received: by mail-ea0-f171.google.com with SMTP id h10so4668631eak.16 for ; Wed, 22 Jan 2014 07:53:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=QZXaAAuHnJB7tznTmIsVUdWtWt6GOAzsD7LvZk8CHds=; b=b1hPkkkLsTLgFaAPzAA/AB0dMLPSS4wQpC5RNSP1O26Zgx5ponOVWjfbEhdScasLEz I23oQc9TzCTxfzohnnZYEaK0Ah72Ic5Tpf1vFinM3sOIs8eRCbSrAO0Esb72h+YwaNfF 8g4OUAypnc7yJcUDXNcFZlOCjNAp+YF3idw5CokftGQ0KfmY23AHf7GdzffwzHbF/7Sz 1bWVOzJMGYU0eI8tWesKYbrtiljUhYD50JVCCZErWdhP08orSHK/+PO5Ex9TMOH/mbYi KLUK47CKBHCe63i/ZVIMSJpeSjnmbYLyhLSoDC/oF5wD9VxQMYD/VYrZ0oVWc+4H2f57 xCxw== X-Received: by 10.14.200.197 with SMTP id z45mr671167een.98.1390405993287; Wed, 22 Jan 2014 07:53:13 -0800 (PST) Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id z49sm28498645eeo.10.2014.01.22.07.53.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Jan 2014 07:53:12 -0800 (PST) Message-ID: <52DFE95F.4000400@gmail.com> Date: Wed, 22 Jan 2014 16:53:03 +0100 From: Tomek Mrugalski User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: dhcpv6bis@ietf.org X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Dhcpv6bis] 2014-01-22 meeting minutes X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 15:53:17 -0000 We had a very good WebEx meeting today and made several decisions. I took some notes during the meeting. Here's the cleaned up version of them. Please correct if I missed or misunderstood anything. Note: All tickets numbers refer to the tickets in out issue tracker: http://trac.tools.ietf.org/group/dhcpv6bis/ Thanks to Bernie for organizing this call. Attendees: Bernie Marcin Michael Sheng Tomek Andrew couldn't make it this time, because of a trip. He asked some tasks be assigned to him. 1. Confirm that XML for 3315 is done. The only outstanding item was to implement soft cross-references. Bernie did that this week (thanks!). We closed tickets #1,#2,#3 and #4. 2. Confirm that XML for 3633 is done. Confirmed. Closing #5. 3. Get over a list of proposed RFCs/drafts to merge. RFC7083 - SOL_MAX_RT and INF_MAX_RT Decision: Add a text that SOL_MAX_RT and INF_MAX_RT should be processed by clients even if status code indicates failure. Incorporate the text and obsolete 7083. RFC6977 - Triggered reconfigure We initially thought that it's about making explicit the currently implicit assumption that the relays do not modify client's messages and based on that info we decided to include clarification that relays do not modify any relayed message (regardless if the message goes up or down). Unfortunately, that is the clarification done in RFC6422. So the decision we made is not valid and this topic will have to be revisited. RFC3736 - stateless DHCPV6 Decision: Add new section for minimal stateless implemention should be. Then obsolete 3736. RFC6355 - DUID-UUID Decision: Include code type 4, reference 6355, do NOT obsolete 6355. RFC6644 - rebind in reconfigure Decision: Incorporate everything. My may discuss with Ted whether to obsolete it, but it seems that the 6644 text will still be technically valid, so we can leave it. RFC6422 - relay supplied options Decision is postponed, as nobody on the call knew what exactly that RFC changes (it updates 3315). draft-ietf-dhc-stateful-issues - The tentative decision was to include all the changes, assuming it progresses (it is in WGLC right now). Tomek will create each section 4.x in issue tracker. draft-ietf-dhc-dhcpv6-unknown-msg - handling by relays Decision was to include the text. It's a relatively simple clarification that relays must forward unknown messages. Bernie proposed to add a section (appendix?) for "Changes from 3315/3633". This will be used by people who are familiar with 3315 and want to see what's changed (e.g. implementors, document authors). 5. Decide on next steps - go over reported issues in the tracker. Segregate them into: a) obvious/easy to do => apply them before merge b) widely supported, but harder to do => apply them after merge c) awaiting-consensus => leave them for discussion on DHC WG - apply/close issues marked as a) - upload new revision - merge - upload new revision - apply/close issues makred as b) - request adoption in DHC - discuss issues from c) group on DHC WG, get consensus on them, apply or reject on a per case basis - WGLC once all issues are closed Marcin asked whether we could start discussions on DHC earlier. Sheng was a bit concerned that WG may say that it did not agree to something. The general conclusion was that it is ok to discuss on DHC whenever we want. 6. Come up with the merge 3633/3315 strategy. This looks like a too big task for a single person, so we'll probably try to split this work among two volunteers. Haven't given much thought about how to do this, but each person being responsible for moving roughly a half of the 3633 sections seems like a good idea. This is to PLAN the merge (what terminology to use, i.e. Requesting Router = DHCPv6 Client for PD) and what will need to be updated in RFC 3315 (new sections to add, sections to update, etc.). Note also that stateful issues draft changes some PD related items so be mindful of this (though those are not yet 'approved'). Michael volunteered for this task and we agreed that this would be also good task for Andrew to help with. 7. Go over reported issues in issue tracker and split into groups. Unfortunately we ran out of time. So Tomek will go over some of the tickets and assign them to interested folks, so everyone will have something to do for the next week or two. Action items: Bernie to submit tickets from bake-offs. Tomek to submit tickets for RFCs/drafts (see agenda item 3 above). Tomek to submit tickets from stateful-issues Tomek to go over existing tasks and assign a couple to every bis team member. Tomek will create milestones (a-trivial/do-now b-larger/do after merge, c-awaiting-consensus, will discuss on DHC) We made a good progress today. Thank you all and safe travels to Andrew! Tomek From leaf.yeh.sdo@gmail.com Wed Jan 22 17:58:41 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4765D1A025E for ; Wed, 22 Jan 2014 17:58:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4 X-Spam-Level: X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_INVITATION=-2, SPF_PASS=-0.001] 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 oNcnBszp_H38 for ; Wed, 22 Jan 2014 17:58:39 -0800 (PST) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 42E461A0147 for ; Wed, 22 Jan 2014 17:58:39 -0800 (PST) Received: by mail-pa0-f43.google.com with SMTP id rd3so1201707pab.30 for ; Wed, 22 Jan 2014 17:58:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:thread-index :content-language; bh=fieXAmd6zpgsd/EXhsO7Dmp31YF5b62plXXTNptoVzU=; b=JdP8cC1JOAbaJcRjvJhEntdbITzIkruJ7NJLQSaWQH3OmEpgvIt70ossxa8+DVQn2o PNpLkLPStg84kpQUwAwmVu3h+EGkqzz8cBipHezZ10meRHTHxNNHBctR5JoDJW4kGNsZ gNQ3mNx3OB4FERAaXLDttmp35VG9DVBlmmHokCoX3aCDbeQSIr/5r0EL2Bn9Qsi2g6Nu BaQqUCOTlEbtW8+k5OmlfUm4iO2LnxXSojbjlVYwBKuDFAU8neY3f3calwin+5qTRByR 9RvdA5OKAMOT9LP4By6S/A3URkAsIZJ47/qtoa1e3RLTr3Hsj7l0Bck6KbdDn9YFqbt4 LRCA== X-Received: by 10.66.190.198 with SMTP id gs6mr5125376pac.49.1390442318671; Wed, 22 Jan 2014 17:58:38 -0800 (PST) Received: from PC ([218.241.103.81]) by mx.google.com with ESMTPSA id cz3sm29422568pbc.9.2014.01.22.17.58.36 for (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 22 Jan 2014 17:58:37 -0800 (PST) From: "Leaf Yeh" To: "'Bernie Volz \(volz\)'" , "'Andrew Yourtchenko \(ayourtch\)'" , References: <489D13FBFA9B3E41812EA89F188F018E1AE2AB2E@xmb-rcd-x04.cisco.com> <52DD6E41.7080708@gmail.com> <52DD6FAB.3090609@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1AE2EB4C@xmb-rcd-x04.cisco.com> In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AE2EB4C@xmb-rcd-x04.cisco.com> Date: Thu, 23 Jan 2014 09:58:33 +0800 Message-ID: <52e0774d.a3b2440a.49f0.6c79@mx.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AQHPFg+BRBK18Eknw0+r8g4RdL27QJqOWRiAgAJ7hNCAALU58A== Content-Language: zh-cn Subject: Re: [Dhcpv6bis] Agenda for dhcpv6bis meeting on 2014-01-22 X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 01:58:41 -0000 BV > This is to PLAN the merge (what terminology to use, i.e. Requesting Router = DHCPv6 Client for PD) and what will need to be updated in RFC 3315 (new sections to add, sections to update, etc.). Note also that stateful issues draft changes some PD related items so be mindful of this (though those are not yet 'approved'). I could be the additional volunteer to build a new list of terminology for DHCPv6bis. Best Regards, Leaf -----Original Message----- From: Dhcpv6bis [mailto:dhcpv6bis-bounces@ietf.org] On Behalf Of Bernie Volz (volz) Sent: Wednesday, January 22, 2014 10:48 PM To: Andrew Yourtchenko (ayourtch); dhcpv6bis@ietf.org Subject: Re: [Dhcpv6bis] Agenda for dhcpv6bis meeting on 2014-01-22 Andrew: We assigned you to work with Michael on X: "X. Come up with the merge 3633/3315 strategy. This looks like a too big task for a single person, so we'll probably try to split this work among two volunteers. Haven't given much thought about how to do this, but each person being responsible for moving roughly a half of the 3633 sections seems like a good idea." This is to PLAN the merge (what terminology to use, i.e. Requesting Router = DHCPv6 Client for PD) and what will need to be updated in RFC 3315 (new sections to add, sections to update, etc.). Note also that stateful issues draft changes some PD related items so be mindful of this (though those are not yet 'approved'). If you are not comfortable with this, let us know and we can assign someone else. - Bernie -----Original Message----- From: Dhcpv6bis [mailto:dhcpv6bis-bounces@ietf.org] On Behalf Of Tomek Mrugalski Sent: Monday, January 20, 2014 1:49 PM To: dhcpv6bis@ietf.org Subject: Re: [Dhcpv6bis] Agenda for dhcpv6bis meeting on 2014-01-22 Oops, Forgot about one extra item: X. Come up with the merge 3633/3315 strategy. This looks like a too big task for a single person, so we'll probably try to split this work among two volunteers. Haven't given much thought about how to do this, but each person being responsible for moving roughly a half of the 3633 sections seems like a good idea. Tomek On 20.01.2014 19:43, Tomek Mrugalski wrote: > Folks, > Here's an agenda for upcoming Wednesday, Jan 22nd meeting > 8:00 EST (14:00 CET, 21:00 CST). Bernie sent out meeting invitation in > a separate mail. > > 1. Confirm that XML for 3315 is done. > One outstanding issue are the cross-references. Bernie said he'll look > at that. So this is likely to be a very quick item. > > 2. Confirm that XML for 3633 is done. > Same as above, except we won't need cross-references as the text will > end up being copied over to 3315bis, so its references will need to be > tweaked anyway. > > 3. Get over the list of RFCs we want to merge. > Tomek will send out a list of candidates. We'll decide for each of > them what to do: > a) reference only > b) copy minimal text (e.g. UUID duid type) and reference the RFC/I-D > c) skip completely > > 4. Discuss authorship > The problem is with the number of authors. RFC Editor recommends to > not have more than 5 authors > (http://www.rfc-editor.org/policy.html#policy.authlist). This is a > soft limit, so we can go over if needed, but going for full list (6 > original > 3315 authors + 5 new ones) will likely not be acceptable. Bernie > proposed (and Tomek agrees) to go with the list of DHCPv6bis team > members and thank 3315 authors in acknowledgement section. We will > also want to thank some people that reported errata or issues. > > 5. Decide on next steps > Proposal: > > - go over reported issues in the tracker. Segregate them into: > a) obvious/easy to do => apply them before merge > b) widely supported, but harder to do => apply them after merge > c) contentious => leave them for discussion on DHC WG > > - apply/close issues marked as a) > - upload new revision > - merge > - upload new revision > - apply/close issues makred as b) > - request adoption in DHC > - discuss issues from c) group on DHC WG, get consensus on them, > apply or reject on a per case basis > - WGLC once all issues are closed > > 6. Go over reported issues in issue tracker and split into groups. > > We'll likely to assign owner to each issue. Such owner will be > responsible for dealing with the issue (and lead any discussions that > may emerge). > > 7. Any other business > > It seems that the majority of the time spent on the meeting will be > about going through the issues in issue tracker. Please take a look at > them prior to the meeting, if possible. > > Folks, keep in mind that this is very late meeting for Sheng, so > please keep the non-essential stuff to minimum. > > Bernie & Tomek > _______________________________________________ Dhcpv6bis mailing list Dhcpv6bis@ietf.org https://www.ietf.org/mailman/listinfo/dhcpv6bis _______________________________________________ Dhcpv6bis mailing list Dhcpv6bis@ietf.org https://www.ietf.org/mailman/listinfo/dhcpv6bis From mcr@sandelman.ca Fri Jan 31 12:48:51 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58F531A0456 for ; Fri, 31 Jan 2014 12:48:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.029 X-Spam-Level: * X-Spam-Status: No, score=1.029 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, T_MIME_NO_TEXT=0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no 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 Z1eBPYUO4lP4 for ; Fri, 31 Jan 2014 12:48:49 -0800 (PST) Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id AC3731A0451 for ; Fri, 31 Jan 2014 12:48:48 -0800 (PST) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id CDEAD20028 for ; Fri, 31 Jan 2014 17:05:23 -0500 (EST) Received: by sandelman.ca (Postfix, from userid 179) id 931B064656; Fri, 31 Jan 2014 15:48:41 -0500 (EST) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 7EEE664655 for ; Fri, 31 Jan 2014 15:48:41 -0500 (EST) From: Michael Richardson To: dhcpv6bis X-Attribution: mcr X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Sender: mcr@sandelman.ca Subject: [Dhcpv6bis] next telecon X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 20:48:51 -0000 --=-=-= I think, if we are doing this every two weeks, that the next one is Feb. 5? If so, I will need to send regrets, as I have to be at my son's school to help put on a winter carnival. (I will attempt to hand out v6 address in a stateful fashion, but I'm not the school's non-competition and privacy policies will let do that. Likely it's privacy extensions or nothing :-). I also have to bring enough prefixes for all 400 kids) -- Michael Richardson , Sandelman Software Works --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQCVAwUBUuwMJ4qHRg3pndX9AQL0pQQAm9VwG6yReLnFr7VmCeQ6GvcLU0Vefv6G ExCkXrQx26q9SbCfr365UkLdY5GiHk+jijZ7VCryT6dywHJwR3H53pwJXnIcpt7p R+UDfN0Mn2uC9Ih9D2TMzRzJlF9BIcxWnU0i9nYIWzxZpI4R4mYVs1WxuaWXXkhV lZAN7glIVqg= =REDp -----END PGP SIGNATURE----- --=-=-=-- From volz@cisco.com Fri Jan 31 14:04:07 2014 Return-Path: X-Original-To: dhcpv6bis@ietfa.amsl.com Delivered-To: dhcpv6bis@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAB461A0426 for ; Fri, 31 Jan 2014 14:04:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.036 X-Spam-Level: X-Spam-Status: No, score=-15.036 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, 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 zCO-TM6de1mK for ; Fri, 31 Jan 2014 14:04:06 -0800 (PST) Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 350731A03A8 for ; Fri, 31 Jan 2014 14:04:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1120; q=dns/txt; s=iport; t=1391205843; x=1392415443; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=v5HKJa4kjMrwGu8YcP79Q8vVxAlvYBM7xvbiOsJgYUM=; b=AufgRi0Hg2lcZu0lCNrTpa7q8PZRXJ7sF03PZjZnMT7/0RqGb1IHVbH+ iDUb9W1Evg2NgqxUgUng6AL25ZCjGTzA8VU4eTceg1A1ARZKlRriUVVat NZFxdOcgKMH2tJkUD1iwCAHeCMQ/pTPpsr8lPkYtt57XmdfbwdkBnPOXx Y=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgkFALAd7FKtJXG+/2dsb2JhbABZgw44vGlPgQ8WAXSDfQEBAQMBAQEBNzQLBQsCAQgYHhAnCyUCBA4Fh3wIDcZVEwSOXzMHgyOBEwSYFpIUgys X-IronPort-AV: E=Sophos;i="4.95,760,1384300800"; d="scan'208";a="298080053" Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-9.cisco.com with ESMTP; 31 Jan 2014 22:04:02 +0000 Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0VM412C020540 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 31 Jan 2014 22:04:01 GMT Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0123.003; Fri, 31 Jan 2014 16:04:01 -0600 From: "Bernie Volz (volz)" To: Michael Richardson Thread-Topic: [Dhcpv6bis] next telecon Thread-Index: AQHPHsXa8RHHcFQdD0OGEJXewQLeOZqfYyXF Date: Fri, 31 Jan 2014 22:04:00 +0000 Message-ID: <678DE37F-D4F6-4A98-A709-C94A84CDE845@cisco.com> References: <27550.1391201321@sandelman.ca> In-Reply-To: <27550.1391201321@sandelman.ca> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: dhcpv6bis Subject: Re: [Dhcpv6bis] next telecon X-BeenThere: dhcpv6bis@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "DHCPv6 \(RFC3315\) bis discussion list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 22:04:08 -0000 I don't think we have a firm schedule for the calls. Nothing set up yet for= the next one. I am on vacation until 2/8 so would not be available. I still haven't done my action item to add the Stateful Issues items into t= he tracker (there's also the Bakeoff items too). - Bernie (from iPad) > On Jan 31, 2014, at 3:48 PM, "Michael Richardson" = wrote: >=20 >=20 > I think, if we are doing this every two weeks, that the next one is Feb. = 5? > If so, I will need to send regrets, as I have to be at my son's school to > help put on a winter carnival. >=20 > (I will attempt to hand out v6 address in a stateful fashion, but I'm not= the > school's non-competition and privacy policies will let do that. Likely it= 's > privacy extensions or nothing :-). I also have to bring enough prefixes = for > all 400 kids) >=20 > -- > Michael Richardson , Sandelman Software Works >=20 >=20 >=20 > _______________________________________________ > Dhcpv6bis mailing list > Dhcpv6bis@ietf.org > https://www.ietf.org/mailman/listinfo/dhcpv6bis