
From bclaise@cisco.com  Tue Dec 11 09:24:14 2012
Return-Path: <bclaise@cisco.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F40B21F850D for <renum@ietfa.amsl.com>; Tue, 11 Dec 2012 09:24:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.023
X-Spam-Level: 
X-Spam-Status: No, score=-10.023 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_48=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DesTXspHzzu0 for <renum@ietfa.amsl.com>; Tue, 11 Dec 2012 09:24:13 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 406D321F84CD for <renum@ietf.org>; Tue, 11 Dec 2012 09:24:13 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qBBHOAit016871; Tue, 11 Dec 2012 18:24:10 +0100 (CET)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qBBHO8fs028797; Tue, 11 Dec 2012 18:24:09 +0100 (CET)
Message-ID: <50C76C38.9000103@cisco.com>
Date: Tue, 11 Dec 2012 18:24:08 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: renum@ietf.org
References: <50C73F18.5000408@cisco.com>
In-Reply-To: <50C73F18.5000408@cisco.com>
X-Forwarded-Message-Id: <50C73F18.5000408@cisco.com>
Content-Type: multipart/alternative; boundary="------------070901080709000007030302"
Subject: [renum] draft-ietf-6renum-enterprise: review
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2012 17:24:14 -0000

This is a multi-part message in MIME format.
--------------070901080709000007030302
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

I've been reviewing draft-ietf-6renum-enterprise

I have a concern with this document. Not really an objection in the form 
of a DISCUSS, but ...
 From the charter, I believe that this document fits the following:

    1. To undertake scenario descriptions, including documentation of
    current capability inventories and existing BCPs, for enterprise
    networks, including managed and unmanaged elements. These texts should
    contribute towards a gap analysis and provide an agreed basis for
    subsequent WG rechartering towards development of solutions (which may
    be more appropriate for other WGs to undertake) and improved practices.
    Operator input will be of high value for this text.

Reading this reading, I asked myself: what is the specific scope of this 
document? I see a mix of scenarios, listing of the existing solutions, 
best current practices, etc... and I'm wondering where this document 
fits in all the IPv6 documents renumbering documents: RFC 5887, this 
document, Enterprise IPv6 Deployment Guidelines 
draft-ietf-v6ops-enterprise-incremental-ipv6-01, rfc4192, etc...
By "etc", I mean searching for "renum" in 
https://www.ietf.org/download/rfc-index.txt.
It seems that many of these documents have the same type of content. Too 
many actually. Don't get me wrong, there is good text in this document.

Bottom line: if someone is interested in renumbering, what is the 
ordered list of documents to be read, with the respective content. My 
conclusion is that there will be a lot of overlap. I would happy to 
stand corrected.

Btw, this document title mentions "guidelines", while BCP is mentioned 
all over.

Note: I did my home trying to find the answer: read RFC 5887, listened 
to the IETF 85 meeting recording, etc...


- A side note!question, and I'm not sure it has to be addressed by this 
draft, but one day, I would like to find an answer.
How does a NMS do a discovery of a pure IPv6 network? With something 
better than ping sweep obviously...


_Editorial_
1.
Section 1, paragraph 1

    PI space is not always available
    for enterprises Therefore, it is desirable to develop mechanisms that
    simplify IPv6 renumbering.

Missing a "."

2.
Section 1, paragraph 1

    However, widespread use of PI might
    create serious BGP4 scaling problems

A reference, or a small explanation, would be welcome

Regards, Benoit





--------------070901080709000007030302
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Dear all,<br>
    <br>
    I've been reviewing draft-ietf-6renum-enterprise<br>
    <div class="moz-forward-container">
      <div class="moz-forward-container"> <br>
        I have a concern with this document. Not really an objection in
        the form of a DISCUSS, but ...<br>
        From the charter, I believe that this document fits the
        following: <br>
        <blockquote> 1. To undertake scenario descriptions, including
          documentation of <br>
          current capability inventories and existing BCPs, for
          enterprise <br>
          networks, including managed and unmanaged elements. These
          texts should <br>
          contribute towards a gap analysis and provide an agreed basis
          for <br>
          subsequent WG rechartering towards development of solutions
          (which may <br>
          be more appropriate for other WGs to undertake) and improved
          practices. <br>
          Operator input will be of high value for this text. <br>
        </blockquote>
        Reading this reading, I asked myself: what is the specific scope
        of this document? I see a mix of scenarios, listing of the
        existing solutions, best current practices, etc... and I'm
        wondering where this document fits in all the IPv6 documents
        renumbering documents: RFC 5887, this document, Enterprise IPv6
        Deployment Guidelines
        draft-ietf-v6ops-enterprise-incremental-ipv6-01, rfc4192, etc...
        <br>
        By "etc", I mean searching for "renum" in <a
          moz-do-not-send="true" class="moz-txt-link-freetext"
          href="https://www.ietf.org/download/rfc-index.txt">https://www.ietf.org/download/rfc-index.txt</a>.<br>
        It seems that many of these documents have the same type of
        content. Too many actually. Don't get me wrong, there is good
        text in this document.<br>
        <br>
        Bottom line: if someone is interested in renumbering, what is
        the ordered list of documents to be read, with the respective
        content. My conclusion is that there will be a lot of overlap. I
        would happy to stand corrected.<br>
        <br>
        Btw, this document title mentions "guidelines", while BCP is
        mentioned all over. <br>
        <br>
        Note: I did my home trying to find the answer: read RFC 5887,
        listened to the IETF 85 meeting recording, etc...<br>
        <br>
        <br>
        - A side note!question, and I'm not sure it has to be addressed
        by this draft, but one day, I would like to find an answer.<br>
        How does a NMS do a discovery of a pure IPv6 network? With
        something better than ping sweep obviously...<br>
        <br>
        <br>
        <u> Editorial</u><br>
        1.<br>
        Section 1, paragraph 1<br>
        <pre class="newpage">   PI space is not always available
   for enterprises Therefore, it is desirable to develop mechanisms that
   simplify IPv6 renumbering.</pre>
        Missing a "."<br>
        <br>
        2.<br>
        Section 1, paragraph 1<br>
        <pre class="newpage">   However, widespread use of PI might
   create serious BGP4 scaling problems 
</pre>
        A reference, or a small explanation, would be welcome<br>
        <br>
        Regards, Benoit<br>
        <br>
      </div>
      <br>
      <br>
    </div>
    <br>
  </body>
</html>

--------------070901080709000007030302--

From rbonica@juniper.net  Tue Dec 11 09:54:46 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C278E21F8440 for <renum@ietfa.amsl.com>; Tue, 11 Dec 2012 09:54:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.139
X-Spam-Level: 
X-Spam-Status: No, score=-103.139 tagged_above=-999 required=5 tests=[AWL=-0.273, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_48=0.6, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8R3OC-tgougw for <renum@ietfa.amsl.com>; Tue, 11 Dec 2012 09:54:44 -0800 (PST)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id A38AE21F843D for <renum@ietf.org>; Tue, 11 Dec 2012 09:54:44 -0800 (PST)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKUMdzZPa6Nj7PiFpEhBI8QfHP6401h6b9@postini.com; Tue, 11 Dec 2012 09:54:44 PST
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 11 Dec 2012 09:54:36 -0800
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Tue, 11 Dec 2012 09:54:35 -0800
Received: from ch1outboundpool.messaging.microsoft.com (216.32.181.181) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Tue, 11 Dec 2012 09:56:43 -0800
Received: from mail154-ch1-R.bigfish.com (10.43.68.251) by CH1EHSOBE008.bigfish.com (10.43.70.58) with Microsoft SMTP Server id 14.1.225.23; Tue, 11 Dec 2012 17:54:28 +0000
Received: from mail154-ch1 (localhost [127.0.0.1])	by mail154-ch1-R.bigfish.com (Postfix) with ESMTP id 2AF5B401C5	for <renum@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Tue, 11 Dec 2012 17:54:28 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.238.5; KIP:(null); UIP:(null); (null); H:BY2PRD0512HT003.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -21
X-BigFish: PS-21(zz9371Ic85fhzz1de0h1202h1e76h1d1ah1d2ahzz16d858h1033IL17326ah8275bh8275dh18c673hz2dh2a8h668h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0h162dh1631h1758h1155h)
Received: from mail154-ch1 (localhost.localdomain [127.0.0.1]) by mail154-ch1 (MessageSwitch) id 1355248466852464_25885; Tue, 11 Dec 2012 17:54:26 +0000 (UTC)
Received: from CH1EHSMHS021.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.233])	by mail154-ch1.bigfish.com (Postfix) with ESMTP id CDBD740005A;	Tue, 11 Dec 2012 17:54:26 +0000 (UTC)
Received: from BY2PRD0512HT003.namprd05.prod.outlook.com (157.56.238.5) by CH1EHSMHS021.bigfish.com (10.43.70.21) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 11 Dec 2012 17:54:26 +0000
Received: from BY2PRD0512MB653.namprd05.prod.outlook.com ([169.254.5.213]) by BY2PRD0512HT003.namprd05.prod.outlook.com ([10.255.243.36]) with mapi id 14.16.0245.002; Tue, 11 Dec 2012 17:54:19 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Benoit Claise <bclaise@cisco.com>, "renum@ietf.org" <renum@ietf.org>
Thread-Topic: draft-ietf-6renum-enterprise: review
Thread-Index: AQHN18RpJZpCsEsViU2iQ4MemitA0JgT3x+A
Date: Tue, 11 Dec 2012 17:54:19 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2501DCE108@BY2PRD0512MB653.namprd05.prod.outlook.com>
References: <50C73F18.5000408@cisco.com> <50C76C38.9000103@cisco.com>
In-Reply-To: <50C76C38.9000103@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: multipart/alternative; boundary="_000_2CF4CB03E2AA464BA0982EC92A02CE2501DCE108BY2PRD0512MB653_"
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%CISCO.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Subject: Re: [renum] draft-ietf-6renum-enterprise: review
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2012 17:54:46 -0000

--_000_2CF4CB03E2AA464BA0982EC92A02CE2501DCE108BY2PRD0512MB653_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks,

Because the document attracted similar comments from another AD, I have rem=
oved the document from Thursday's telechat so that the WG could take whatev=
er time it needed to discuss the matter.

If we decided to move forward with this document, as is, I will put it back=
 on the next telechat agenda.

Authors, could I ask you to respond to Benoit?

                                              Ron


From: Benoit Claise [mailto:bclaise@cisco.com]
Sent: Tuesday, December 11, 2012 12:24 PM
To: renum@ietf.org
Cc: Ronald Bonica
Subject: draft-ietf-6renum-enterprise: review

Dear all,

I've been reviewing draft-ietf-6renum-enterprise

I have a concern with this document. Not really an objection in the form of=
 a DISCUSS, but ...
>From the charter, I believe that this document fits the following:
1. To undertake scenario descriptions, including documentation of
current capability inventories and existing BCPs, for enterprise
networks, including managed and unmanaged elements. These texts should
contribute towards a gap analysis and provide an agreed basis for
subsequent WG rechartering towards development of solutions (which may
be more appropriate for other WGs to undertake) and improved practices.
Operator input will be of high value for this text.
Reading this reading, I asked myself: what is the specific scope of this do=
cument? I see a mix of scenarios, listing of the existing solutions, best c=
urrent practices, etc... and I'm wondering where this document fits in all =
the IPv6 documents renumbering documents: RFC 5887, this document, Enterpri=
se IPv6 Deployment Guidelines draft-ietf-v6ops-enterprise-incremental-ipv6-=
01, rfc4192, etc...
By "etc", I mean searching for "renum" in https://www.ietf.org/download/rfc=
-index.txt.
It seems that many of these documents have the same type of content. Too ma=
ny actually. Don't get me wrong, there is good text in this document.

Bottom line: if someone is interested in renumbering, what is the ordered l=
ist of documents to be read, with the respective content. My conclusion is =
that there will be a lot of overlap. I would happy to stand corrected.

Btw, this document title mentions "guidelines", while BCP is mentioned all =
over.

Note: I did my home trying to find the answer: read RFC 5887, listened to t=
he IETF 85 meeting recording, etc...


- A side note!question, and I'm not sure it has to be addressed by this dra=
ft, but one day, I would like to find an answer.
How does a NMS do a discovery of a pure IPv6 network? With something better=
 than ping sweep obviously...


Editorial
1.
Section 1, paragraph 1

   PI space is not always available

   for enterprises Therefore, it is desirable to develop mechanisms that

   simplify IPv6 renumbering.
Missing a "."

2.
Section 1, paragraph 1

   However, widespread use of PI might

   create serious BGP4 scaling problems
A reference, or a small explanation, would be welcome

Regards, Benoit



--_000_2CF4CB03E2AA464BA0982EC92A02CE2501DCE108BY2PRD0512MB653_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Folks,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Because the document attr=
acted similar comments from another AD, I have removed the document from Th=
ursday&#8217;s telechat so that the WG could take whatever time
 it needed to discuss the matter. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">If we decided to move for=
ward with this document, as is, I will put it back on the next telechat age=
nda.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Authors, could I ask you =
to respond to Benoit?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Ron<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext"> Benoit Claise [mailto:bclaise@cisco.com]
<br>
<b>Sent:</b> Tuesday, December 11, 2012 12:24 PM<br>
<b>To:</b> renum@ietf.org<br>
<b>Cc:</b> Ronald Bonica<br>
<b>Subject:</b> draft-ietf-6renum-enterprise: review<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dear all,<br>
<br>
I've been reviewing draft-ietf-6renum-enterprise<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
I have a concern with this document. Not really an objection in the form of=
 a DISCUSS, but ...<br>
>From the charter, I believe that this document fits the following: <o:p></o=
:p></p>
<p class=3D"MsoNormal">1. To undertake scenario descriptions, including doc=
umentation of
<br>
current capability inventories and existing BCPs, for enterprise <br>
networks, including managed and unmanaged elements. These texts should <br>
contribute towards a gap analysis and provide an agreed basis for <br>
subsequent WG rechartering towards development of solutions (which may <br>
be more appropriate for other WGs to undertake) and improved practices. <br=
>
Operator input will be of high value for this text. <o:p></o:p></p>
<p class=3D"MsoNormal">Reading this reading, I asked myself: what is the sp=
ecific scope of this document? I see a mix of scenarios, listing of the exi=
sting solutions, best current practices, etc... and I'm wondering where thi=
s document fits in all the IPv6 documents
 renumbering documents: RFC 5887, this document, Enterprise IPv6 Deployment=
 Guidelines draft-ietf-v6ops-enterprise-incremental-ipv6-01, rfc4192, etc..=
.
<br>
By &quot;etc&quot;, I mean searching for &quot;renum&quot; in <a href=3D"ht=
tps://www.ietf.org/download/rfc-index.txt">
https://www.ietf.org/download/rfc-index.txt</a>.<br>
It seems that many of these documents have the same type of content. Too ma=
ny actually. Don't get me wrong, there is good text in this document.<br>
<br>
Bottom line: if someone is interested in renumbering, what is the ordered l=
ist of documents to be read, with the respective content. My conclusion is =
that there will be a lot of overlap. I would happy to stand corrected.<br>
<br>
Btw, this document title mentions &quot;guidelines&quot;, while BCP is ment=
ioned all over. <br>
<br>
Note: I did my home trying to find the answer: read RFC 5887, listened to t=
he IETF 85 meeting recording, etc...<br>
<br>
<br>
- A side note!question, and I'm not sure it has to be addressed by this dra=
ft, but one day, I would like to find an answer.<br>
How does a NMS do a discovery of a pure IPv6 network? With something better=
 than ping sweep obviously...<br>
<br>
<br>
<u>Editorial</u><br>
1.<br>
Section 1, paragraph 1<o:p></o:p></p>
<pre>&nbsp;&nbsp; PI space is not always available<o:p></o:p></pre>
<pre>&nbsp;&nbsp; for enterprises Therefore, it is desirable to develop mec=
hanisms that<o:p></o:p></pre>
<pre>&nbsp;&nbsp; simplify IPv6 renumbering.<o:p></o:p></pre>
<p class=3D"MsoNormal">Missing a &quot;.&quot;<br>
<br>
2.<br>
Section 1, paragraph 1<o:p></o:p></p>
<pre>&nbsp;&nbsp; However, widespread use of PI might<o:p></o:p></pre>
<pre>&nbsp;&nbsp; create serious BGP4 scaling problems <o:p></o:p></pre>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">A reference, or a sma=
ll explanation, would be welcome<br>
<br>
Regards, Benoit<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_2CF4CB03E2AA464BA0982EC92A02CE2501DCE108BY2PRD0512MB653_--

From jiangsheng@huawei.com  Wed Dec 12 00:56:05 2012
Return-Path: <jiangsheng@huawei.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B7BF21F8951 for <renum@ietfa.amsl.com>; Wed, 12 Dec 2012 00:56:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.264
X-Spam-Level: 
X-Spam-Status: No, score=-6.264 tagged_above=-999 required=5 tests=[AWL=-0.266, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_48=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BEdn5FhOfqmH for <renum@ietfa.amsl.com>; Wed, 12 Dec 2012 00:56:04 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3005421F894E for <renum@ietf.org>; Wed, 12 Dec 2012 00:56:03 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AMK37325; Wed, 12 Dec 2012 08:56:02 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 12 Dec 2012 08:55:11 +0000
Received: from SZXEML413-HUB.china.huawei.com (10.82.67.152) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 12 Dec 2012 16:56:00 +0800
Received: from SZXEML545-MBS.china.huawei.com ([169.254.2.174]) by szxeml413-hub.china.huawei.com ([10.82.67.152]) with mapi id 14.01.0323.003; Wed, 12 Dec 2012 16:55:50 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ronald Bonica <rbonica@juniper.net>, Benoit Claise <bclaise@cisco.com>, "renum@ietf.org" <renum@ietf.org>
Thread-Topic: draft-ietf-6renum-enterprise: review
Thread-Index: AQHN18iivnxTqWIYdEaNunfic33G3JgU17CA
Date: Wed, 12 Dec 2012 08:55:49 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B9239FD4003@szxeml545-mbs.china.huawei.com>
References: <50C73F18.5000408@cisco.com> <50C76C38.9000103@cisco.com> <2CF4CB03E2AA464BA0982EC92A02CE2501DCE108@BY2PRD0512MB653.namprd05.prod.outlook.com>
In-Reply-To: <2CF4CB03E2AA464BA0982EC92A02CE2501DCE108@BY2PRD0512MB653.namprd05.prod.outlook.com>
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.140]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B9239FD4003szxeml545mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [renum] draft-ietf-6renum-enterprise: review
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 08:56:05 -0000

--_000_5D36713D8A4E7348A7E10DF7437A4B9239FD4003szxeml545mbschi_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksIEJlbm9pdCAmIFJvbiwNCg0KSXQgd2FzIHRoZSBjb25jbHVzaW9uIGZyb20gdGhlIFdHIHdh
cyBmYWlybHkgY2xlYXIgdGhhdCB3ZSB3ZXJlIG5vdCByZWFsbHkgbWFraW5nIGFueSBub3JtYXRp
dmUgcmVjb21tZW5kYXRpb25zLiBCdXQgd2UgcHJvYmFibHkgbmVlZCBhIG5ldyB2ZXJzaW9uIGFu
eXdheSBmb3IgY2xhcmlmaWNhdGlvbnMsIGJhc2VkIG9uIHRoZSBvdGhlciByZXZpZXdzLg0KDQpG
b3Igb3ZlcmxhcHBpbmcsIHllcywgdGhlcmUgYXJlIG1hbnkgZG9jdW1lbnQgbWVudGlvbmVkIHJl
bnVtYmVyaW5nLCBvbmx5IGJlY2F1c2UgaXQgaXMgYSBjb21tb24gaXNzdWUuIERpZmZlcmVudCBm
cm9tIG90aGVyIGRvY3VtZW50cyB0aGF0IG1lbnRpb24gcmVudW1iZXJpbmcgYXMgYSBtaW5vciBy
ZWxldmFudCBjb25zaWRlcmF0aW9uLCB0aGUgNnJlbnVtLWVudGVycHJpc2UgaXMgZGVkaWNhdGVk
IGZvciByZW51bWJlcmluZyBpc3N1ZS4gSXQgZm9jdXNlcyBvbiBlbnRlcnByaXNlIHNjZW5hcmlv
cyBhbmQgbWFrZXMgYSBjb21wcmVoZW5zaXZlIGFuYWx5c2lzLCB3aGljaCBpcyBub3QgcHJvdmlk
ZWQgYnkgdGhlIG90aGVyIGRvY3VtZW50cy4NCg0KQlRXLCBCZW5vaXTigJlzIGVkaXRvcmlhbCBj
b21tZW50cyBoYXMgYmVlbiBmaXhlZCBpbiB0aGUgb25nb2luZyB2ZXJzaW9uLg0KDQpCZXN0IHJl
Z2FyZHMsDQoNClNoZW5nLCBCaW5nLCBCcmFpbg0KDQpGcm9tOiByZW51bS1ib3VuY2VzQGlldGYu
b3JnIFttYWlsdG86cmVudW0tYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFJvbmFsZCBC
b25pY2ENClNlbnQ6IFdlZG5lc2RheSwgRGVjZW1iZXIgMTIsIDIwMTIgMTo1NCBBTQ0KVG86IEJl
bm9pdCBDbGFpc2U7IHJlbnVtQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW3JlbnVtXSBkcmFmdC1p
ZXRmLTZyZW51bS1lbnRlcnByaXNlOiByZXZpZXcNCg0KRm9sa3MsDQoNCkJlY2F1c2UgdGhlIGRv
Y3VtZW50IGF0dHJhY3RlZCBzaW1pbGFyIGNvbW1lbnRzIGZyb20gYW5vdGhlciBBRCwgSSBoYXZl
IHJlbW92ZWQgdGhlIGRvY3VtZW50IGZyb20gVGh1cnNkYXnigJlzIHRlbGVjaGF0IHNvIHRoYXQg
dGhlIFdHIGNvdWxkIHRha2Ugd2hhdGV2ZXIgdGltZSBpdCBuZWVkZWQgdG8gZGlzY3VzcyB0aGUg
bWF0dGVyLg0KDQpJZiB3ZSBkZWNpZGVkIHRvIG1vdmUgZm9yd2FyZCB3aXRoIHRoaXMgZG9jdW1l
bnQsIGFzIGlzLCBJIHdpbGwgcHV0IGl0IGJhY2sgb24gdGhlIG5leHQgdGVsZWNoYXQgYWdlbmRh
Lg0KDQpBdXRob3JzLCBjb3VsZCBJIGFzayB5b3UgdG8gcmVzcG9uZCB0byBCZW5vaXQ/DQoNCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBSb24NCg0KDQpGcm9t
OiBCZW5vaXQgQ2xhaXNlIFttYWlsdG86YmNsYWlzZUBjaXNjby5jb21dDQpTZW50OiBUdWVzZGF5
LCBEZWNlbWJlciAxMSwgMjAxMiAxMjoyNCBQTQ0KVG86IHJlbnVtQGlldGYub3JnDQpDYzogUm9u
YWxkIEJvbmljYQ0KU3ViamVjdDogZHJhZnQtaWV0Zi02cmVudW0tZW50ZXJwcmlzZTogcmV2aWV3
DQoNCkRlYXIgYWxsLA0KDQpJJ3ZlIGJlZW4gcmV2aWV3aW5nIGRyYWZ0LWlldGYtNnJlbnVtLWVu
dGVycHJpc2UNCg0KSSBoYXZlIGEgY29uY2VybiB3aXRoIHRoaXMgZG9jdW1lbnQuIE5vdCByZWFs
bHkgYW4gb2JqZWN0aW9uIGluIHRoZSBmb3JtIG9mIGEgRElTQ1VTUywgYnV0IC4uLg0KRnJvbSB0
aGUgY2hhcnRlciwgSSBiZWxpZXZlIHRoYXQgdGhpcyBkb2N1bWVudCBmaXRzIHRoZSBmb2xsb3dp
bmc6DQoxLiBUbyB1bmRlcnRha2Ugc2NlbmFyaW8gZGVzY3JpcHRpb25zLCBpbmNsdWRpbmcgZG9j
dW1lbnRhdGlvbiBvZg0KY3VycmVudCBjYXBhYmlsaXR5IGludmVudG9yaWVzIGFuZCBleGlzdGlu
ZyBCQ1BzLCBmb3IgZW50ZXJwcmlzZQ0KbmV0d29ya3MsIGluY2x1ZGluZyBtYW5hZ2VkIGFuZCB1
bm1hbmFnZWQgZWxlbWVudHMuIFRoZXNlIHRleHRzIHNob3VsZA0KY29udHJpYnV0ZSB0b3dhcmRz
IGEgZ2FwIGFuYWx5c2lzIGFuZCBwcm92aWRlIGFuIGFncmVlZCBiYXNpcyBmb3INCnN1YnNlcXVl
bnQgV0cgcmVjaGFydGVyaW5nIHRvd2FyZHMgZGV2ZWxvcG1lbnQgb2Ygc29sdXRpb25zICh3aGlj
aCBtYXkNCmJlIG1vcmUgYXBwcm9wcmlhdGUgZm9yIG90aGVyIFdHcyB0byB1bmRlcnRha2UpIGFu
ZCBpbXByb3ZlZCBwcmFjdGljZXMuDQpPcGVyYXRvciBpbnB1dCB3aWxsIGJlIG9mIGhpZ2ggdmFs
dWUgZm9yIHRoaXMgdGV4dC4NClJlYWRpbmcgdGhpcyByZWFkaW5nLCBJIGFza2VkIG15c2VsZjog
d2hhdCBpcyB0aGUgc3BlY2lmaWMgc2NvcGUgb2YgdGhpcyBkb2N1bWVudD8gSSBzZWUgYSBtaXgg
b2Ygc2NlbmFyaW9zLCBsaXN0aW5nIG9mIHRoZSBleGlzdGluZyBzb2x1dGlvbnMsIGJlc3QgY3Vy
cmVudCBwcmFjdGljZXMsIGV0Yy4uLiBhbmQgSSdtIHdvbmRlcmluZyB3aGVyZSB0aGlzIGRvY3Vt
ZW50IGZpdHMgaW4gYWxsIHRoZSBJUHY2IGRvY3VtZW50cyByZW51bWJlcmluZyBkb2N1bWVudHM6
IFJGQyA1ODg3LCB0aGlzIGRvY3VtZW50LCBFbnRlcnByaXNlIElQdjYgRGVwbG95bWVudCBHdWlk
ZWxpbmVzIGRyYWZ0LWlldGYtdjZvcHMtZW50ZXJwcmlzZS1pbmNyZW1lbnRhbC1pcHY2LTAxLCBy
ZmM0MTkyLCBldGMuLi4NCkJ5ICJldGMiLCBJIG1lYW4gc2VhcmNoaW5nIGZvciAicmVudW0iIGlu
IGh0dHBzOi8vd3d3LmlldGYub3JnL2Rvd25sb2FkL3JmYy1pbmRleC50eHQuDQpJdCBzZWVtcyB0
aGF0IG1hbnkgb2YgdGhlc2UgZG9jdW1lbnRzIGhhdmUgdGhlIHNhbWUgdHlwZSBvZiBjb250ZW50
LiBUb28gbWFueSBhY3R1YWxseS4gRG9uJ3QgZ2V0IG1lIHdyb25nLCB0aGVyZSBpcyBnb29kIHRl
eHQgaW4gdGhpcyBkb2N1bWVudC4NCg0KQm90dG9tIGxpbmU6IGlmIHNvbWVvbmUgaXMgaW50ZXJl
c3RlZCBpbiByZW51bWJlcmluZywgd2hhdCBpcyB0aGUgb3JkZXJlZCBsaXN0IG9mIGRvY3VtZW50
cyB0byBiZSByZWFkLCB3aXRoIHRoZSByZXNwZWN0aXZlIGNvbnRlbnQuIE15IGNvbmNsdXNpb24g
aXMgdGhhdCB0aGVyZSB3aWxsIGJlIGEgbG90IG9mIG92ZXJsYXAuIEkgd291bGQgaGFwcHkgdG8g
c3RhbmQgY29ycmVjdGVkLg0KDQpCdHcsIHRoaXMgZG9jdW1lbnQgdGl0bGUgbWVudGlvbnMgImd1
aWRlbGluZXMiLCB3aGlsZSBCQ1AgaXMgbWVudGlvbmVkIGFsbCBvdmVyLg0KDQpOb3RlOiBJIGRp
ZCBteSBob21lIHRyeWluZyB0byBmaW5kIHRoZSBhbnN3ZXI6IHJlYWQgUkZDIDU4ODcsIGxpc3Rl
bmVkIHRvIHRoZSBJRVRGIDg1IG1lZXRpbmcgcmVjb3JkaW5nLCBldGMuLi4NCg0KDQotIEEgc2lk
ZSBub3RlIXF1ZXN0aW9uLCBhbmQgSSdtIG5vdCBzdXJlIGl0IGhhcyB0byBiZSBhZGRyZXNzZWQg
YnkgdGhpcyBkcmFmdCwgYnV0IG9uZSBkYXksIEkgd291bGQgbGlrZSB0byBmaW5kIGFuIGFuc3dl
ci4NCkhvdyBkb2VzIGEgTk1TIGRvIGEgZGlzY292ZXJ5IG9mIGEgcHVyZSBJUHY2IG5ldHdvcms/
IFdpdGggc29tZXRoaW5nIGJldHRlciB0aGFuIHBpbmcgc3dlZXAgb2J2aW91c2x5Li4uDQoNCg0K
RWRpdG9yaWFsDQoxLg0KU2VjdGlvbiAxLCBwYXJhZ3JhcGggMQ0KDQogICBQSSBzcGFjZSBpcyBu
b3QgYWx3YXlzIGF2YWlsYWJsZQ0KDQogICBmb3IgZW50ZXJwcmlzZXMgVGhlcmVmb3JlLCBpdCBp
cyBkZXNpcmFibGUgdG8gZGV2ZWxvcCBtZWNoYW5pc21zIHRoYXQNCg0KICAgc2ltcGxpZnkgSVB2
NiByZW51bWJlcmluZy4NCk1pc3NpbmcgYSAiLiINCg0KMi4NClNlY3Rpb24gMSwgcGFyYWdyYXBo
IDENCg0KICAgSG93ZXZlciwgd2lkZXNwcmVhZCB1c2Ugb2YgUEkgbWlnaHQNCg0KICAgY3JlYXRl
IHNlcmlvdXMgQkdQNCBzY2FsaW5nIHByb2JsZW1zDQpBIHJlZmVyZW5jZSwgb3IgYSBzbWFsbCBl
eHBsYW5hdGlvbiwgd291bGQgYmUgd2VsY29tZQ0KDQpSZWdhcmRzLCBCZW5vaXQNCg0KDQo=

--_000_5D36713D8A4E7348A7E10DF7437A4B9239FD4003szxeml545mbschi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6eD0idXJuOnNjaGVtYXMtbWljcm9z
b2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zOnA9InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206
b2ZmaWNlOnBvd2VycG9pbnQiIHhtbG5zOmE9InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2Zm
aWNlOmFjY2VzcyIgeG1sbnM6ZHQ9InV1aWQ6QzJGNDEwMTAtNjVCMy0xMWQxLUEyOUYtMDBBQTAw
QzE0ODgyIiB4bWxuczpzPSJ1dWlkOkJEQzZFM0YwLTZEQTMtMTFkMS1BMkEzLTAwQUEwMEMxNDg4
MiIgeG1sbnM6cnM9InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206cm93c2V0IiB4bWxuczp6PSIj
Um93c2V0U2NoZW1hIiB4bWxuczpiPSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpw
dWJsaXNoZXIiIHhtbG5zOnNzPSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpzcHJl
YWRzaGVldCIgeG1sbnM6Yz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6Y29tcG9u
ZW50OnNwcmVhZHNoZWV0IiB4bWxuczpvZGM9InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2Zm
aWNlOm9kYyIgeG1sbnM6b2E9InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOmFjdGl2
YXRpb24iIHhtbG5zOmh0bWw9Imh0dHA6Ly93d3cudzMub3JnL1RSL1JFQy1odG1sNDAiIHhtbG5z
OnE9Imh0dHA6Ly9zY2hlbWFzLnhtbHNvYXAub3JnL3NvYXAvZW52ZWxvcGUvIiB4bWxuczpydGM9
Imh0dHA6Ly9taWNyb3NvZnQuY29tL29mZmljZW5ldC9jb25mZXJlbmNpbmciIHhtbG5zOkQ9IkRB
VjoiIHhtbG5zOlJlcGw9Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vcmVwbC8iIHhtbG5z
Om10PSJodHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL3NoYXJlcG9pbnQvc29hcC9tZWV0aW5n
cy8iIHhtbG5zOngyPSJodHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS9leGNlbC8y
MDAzL3htbCIgeG1sbnM6cHBkYT0iaHR0cDovL3d3dy5wYXNzcG9ydC5jb20vTmFtZVNwYWNlLnhz
ZCIgeG1sbnM6b2lzPSJodHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL3NoYXJlcG9pbnQvc29h
cC9vaXMvIiB4bWxuczpkaXI9Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vc2hhcmVwb2lu
dC9zb2FwL2RpcmVjdG9yeS8iIHhtbG5zOmRzPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwLzA5L3ht
bGRzaWcjIiB4bWxuczpkc3A9Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vc2hhcmVwb2lu
dC9kc3AiIHhtbG5zOnVkYz0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9kYXRhL3VkYyIg
eG1sbnM6eHNkPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYSIgeG1sbnM6c3ViPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL3NoYXJlcG9pbnQvc29hcC8yMDAyLzEvYWxlcnRz
LyIgeG1sbnM6ZWM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDEvMDQveG1sZW5jIyIgeG1sbnM6c3A9
Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vc2hhcmVwb2ludC8iIHhtbG5zOnNwcz0iaHR0
cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9zaGFyZXBvaW50L3NvYXAvIiB4bWxuczp4c2k9Imh0
dHA6Ly93d3cudzMub3JnLzIwMDEvWE1MU2NoZW1hLWluc3RhbmNlIiB4bWxuczp1ZGNzPSJodHRw
Oi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL2RhdGEvdWRjL3NvYXAiIHhtbG5zOnVkY3hmPSJodHRw
Oi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL2RhdGEvdWRjL3htbGZpbGUiIHhtbG5zOnVkY3AycD0i
aHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9kYXRhL3VkYy9wYXJ0dG9wYXJ0IiB4bWxuczp3
Zj0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9zaGFyZXBvaW50L3NvYXAvd29ya2Zsb3cv
IiB4bWxuczpkc3NzPSJodHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA2L2Rp
Z3NpZy1zZXR1cCIgeG1sbnM6ZHNzaT0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9vZmZp
Y2UvMjAwNi9kaWdzaWciIHhtbG5zOm1kc3NpPSJodHRwOi8vc2NoZW1hcy5vcGVueG1sZm9ybWF0
cy5vcmcvcGFja2FnZS8yMDA2L2RpZ2l0YWwtc2lnbmF0dXJlIiB4bWxuczptdmVyPSJodHRwOi8v
c2NoZW1hcy5vcGVueG1sZm9ybWF0cy5vcmcvbWFya3VwLWNvbXBhdGliaWxpdHkvMjAwNiIgeG1s
bnM6bT0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4
bWxuczptcmVscz0iaHR0cDovL3NjaGVtYXMub3BlbnhtbGZvcm1hdHMub3JnL3BhY2thZ2UvMjAw
Ni9yZWxhdGlvbnNoaXBzIiB4bWxuczpzcHdwPSJodHRwOi8vbWljcm9zb2Z0LmNvbS9zaGFyZXBv
aW50L3dlYnBhcnRwYWdlcyIgeG1sbnM6ZXgxMnQ9Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5j
b20vZXhjaGFuZ2Uvc2VydmljZXMvMjAwNi90eXBlcyIgeG1sbnM6ZXgxMm09Imh0dHA6Ly9zY2hl
bWFzLm1pY3Jvc29mdC5jb20vZXhjaGFuZ2Uvc2VydmljZXMvMjAwNi9tZXNzYWdlcyIgeG1sbnM6
cHB0c2w9Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vc2hhcmVwb2ludC9zb2FwL1NsaWRl
TGlicmFyeS8iIHhtbG5zOnNwc2w9Imh0dHA6Ly9taWNyb3NvZnQuY29tL3dlYnNlcnZpY2VzL1No
YXJlUG9pbnRQb3J0YWxTZXJ2ZXIvUHVibGlzaGVkTGlua3NTZXJ2aWNlIiB4bWxuczpaPSJ1cm46
c2NoZW1hcy1taWNyb3NvZnQtY29tOiIgeG1sbnM6c3Q9IiYjMTsiIHhtbG5zPSJodHRwOi8vd3d3
LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVpdj0iQ29udGVu
dC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1ldGEgbmFtZT0i
R2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxMiAoZmlsdGVyZWQgbWVkaXVtKSI+
DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFjZQ0KCXtmb250
LWZhbWlseTrlrovkvZM7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1IDMgNSA0
IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0x
OjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IlxA5a6L
5L2TIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCkBmb250LWZhY2UNCgl7Zm9u
dC1mYW1pbHk6VGFob21hOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30NCkBmb250
LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q29uc29sYXM7DQoJcGFub3NlLTE6MiAxMSA2IDkgMiAyIDQg
MyAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3Jt
YWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7
DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2Vy
aWYiOw0KCWNvbG9yOmJsYWNrO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGlu
ZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30N
CnByZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwg6aKE
6K6+5qC85byPIENoYXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0K
CWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsNCgljb2xvcjpi
bGFjazt9DQpzcGFuLkhUTUxDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJIVE1MIOmihOiuvuagvOW8
jyBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwg
6aKE6K6+5qC85byPIjsNCglmb250LWZhbWlseToiQ291cmllciBOZXciOw0KCWNvbG9yOmJsYWNr
O30NCnAuSFRNTFByZWZvcm1hdHRlZCwgbGkuSFRNTFByZWZvcm1hdHRlZCwgZGl2LkhUTUxQcmVm
b3JtYXR0ZWQNCgl7bXNvLXN0eWxlLW5hbWU6IkhUTUwgUHJlZm9ybWF0dGVkIjsNCgltc28tc3R5
bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4t
Ym90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMg
TmV3IFJvbWFuIiwic2VyaWYiOw0KCWNvbG9yOmJsYWNrO30NCnNwYW4uSFRNTFByZWZvcm1hdHRl
ZENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQiOw0K
CWZvbnQtZmFtaWx5OkNvbnNvbGFzOw0KCWNvbG9yOmJsYWNrO30NCnNwYW4uRW1haWxTdHlsZTIx
DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fu
cy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWlsU3R5bGUyMg0KCXttc28tc3R5
bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy
aWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6
ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7
c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBw
dDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+
PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBz
cGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4
bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIg
ZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4N
Cjxib2R5IGJnY29sb3I9IndoaXRlIiBsYW5nPSJaSC1DTiIgbGluaz0iYmx1ZSIgdmxpbms9InB1
cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5I
aSwgQmVub2l0ICZhbXA7IFJvbiw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+
SXQgd2FzIHRoZSBjb25jbHVzaW9uIGZyb20gdGhlIFdHIHdhcyBmYWlybHkgY2xlYXIgdGhhdCB3
ZSB3ZXJlIG5vdCByZWFsbHkgbWFraW5nIGFueSBub3JtYXRpdmUgcmVjb21tZW5kYXRpb25zLiBC
dXQgd2UgcHJvYmFibHkgbmVlZCBhIG5ldyB2ZXJzaW9uDQogYW55d2F5IGZvciBjbGFyaWZpY2F0
aW9ucywgYmFzZWQgb24gdGhlIG90aGVyIHJldmlld3MuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv
bG9yOiMxRjQ5N0QiPkZvciBvdmVybGFwcGluZywgeWVzLCB0aGVyZSBhcmUgbWFueSBkb2N1bWVu
dCBtZW50aW9uZWQgcmVudW1iZXJpbmcsIG9ubHkgYmVjYXVzZSBpdCBpcyBhIGNvbW1vbiBpc3N1
ZS4gRGlmZmVyZW50IGZyb20gb3RoZXIgZG9jdW1lbnRzIHRoYXQgbWVudGlvbg0KIHJlbnVtYmVy
aW5nIGFzIGEgbWlub3IgcmVsZXZhbnQgY29uc2lkZXJhdGlvbiwgdGhlIDZyZW51bS1lbnRlcnBy
aXNlIGlzIGRlZGljYXRlZCBmb3IgcmVudW1iZXJpbmcgaXNzdWUuIEl0IGZvY3VzZXMgb24gZW50
ZXJwcmlzZSBzY2VuYXJpb3MgYW5kIG1ha2VzIGEgY29tcHJlaGVuc2l2ZSBhbmFseXNpcywgd2hp
Y2ggaXMgbm90IHByb3ZpZGVkIGJ5IHRoZSBvdGhlciBkb2N1bWVudHMuPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkJUVywgQmVub2l04oCZcyBlZGl0b3JpYWwgY29tbWVudHMg
aGFzIGJlZW4gZml4ZWQgaW4gdGhlIG9uZ29pbmcgdmVyc2lvbi48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
c2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6IzFGNDk3RCI+QmVzdCByZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv
cjojMUY0OTdEIj5TaGVuZywgQmluZywgQnJhaW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9
ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNt
IDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpz
b2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv
bG9yOndpbmRvd3RleHQiPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6d2luZG93dGV4dCI+IHJlbnVtLWJvdW5jZXNAaWV0Zi5vcmcg
W21haWx0bzpyZW51bS1ib3VuY2VzQGlldGYub3JnXQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5Sb25h
bGQgQm9uaWNhPGJyPg0KPGI+U2VudDo8L2I+IFdlZG5lc2RheSwgRGVjZW1iZXIgMTIsIDIwMTIg
MTo1NCBBTTxicj4NCjxiPlRvOjwvYj4gQmVub2l0IENsYWlzZTsgcmVudW1AaWV0Zi5vcmc8YnI+
DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtyZW51bV0gZHJhZnQtaWV0Zi02cmVudW0tZW50ZXJwcmlz
ZTogcmV2aWV3PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkZvbGtzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv
cjojMUY0OTdEIj5CZWNhdXNlIHRoZSBkb2N1bWVudCBhdHRyYWN0ZWQgc2ltaWxhciBjb21tZW50
cyBmcm9tIGFub3RoZXIgQUQsIEkgaGF2ZSByZW1vdmVkIHRoZSBkb2N1bWVudCBmcm9tIFRodXJz
ZGF54oCZcyB0ZWxlY2hhdCBzbyB0aGF0IHRoZSBXRyBjb3VsZCB0YWtlDQogd2hhdGV2ZXIgdGlt
ZSBpdCBuZWVkZWQgdG8gZGlzY3VzcyB0aGUgbWF0dGVyLiA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+SWYgd2UgZGVjaWRlZCB0byBtb3ZlIGZvcndhcmQgd2l0aCB0aGlzIGRv
Y3VtZW50LCBhcyBpcywgSSB3aWxsIHB1dCBpdCBiYWNrIG9uIHRoZSBuZXh0IHRlbGVjaGF0IGFn
ZW5kYS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+QXV0aG9ycywgY291bGQg
SSBhc2sgeW91IHRvIHJlc3BvbmQgdG8gQmVub2l0PzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv
cjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgUm9u
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUg
MS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9y
ZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNt
IDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOndpbmRvd3RleHQiPkZyb206PC9zcGFuPjwvYj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6d2luZG93dGV4dCI+IEJl
bm9pdCBDbGFpc2UgW21haWx0bzpiY2xhaXNlQGNpc2NvLmNvbV0NCjxicj4NCjxiPlNlbnQ6PC9i
PiBUdWVzZGF5LCBEZWNlbWJlciAxMSwgMjAxMiAxMjoyNCBQTTxicj4NCjxiPlRvOjwvYj4gcmVu
dW1AaWV0Zi5vcmc8YnI+DQo8Yj5DYzo8L2I+IFJvbmFsZCBCb25pY2E8YnI+DQo8Yj5TdWJqZWN0
OjwvYj4gZHJhZnQtaWV0Zi02cmVudW0tZW50ZXJwcmlzZTogcmV2aWV3PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyI+RGVhciBhbGwsPGJyPg0KPGJyPg0KSSd2ZSBiZWVuIHJldmll
d2luZyBkcmFmdC1pZXRmLTZyZW51bS1lbnRlcnByaXNlPG86cD48L286cD48L3NwYW4+PC9wPg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PGJy
Pg0KSSBoYXZlIGEgY29uY2VybiB3aXRoIHRoaXMgZG9jdW1lbnQuIE5vdCByZWFsbHkgYW4gb2Jq
ZWN0aW9uIGluIHRoZSBmb3JtIG9mIGEgRElTQ1VTUywgYnV0IC4uLjxicj4NCkZyb20gdGhlIGNo
YXJ0ZXIsIEkgYmVsaWV2ZSB0aGF0IHRoaXMgZG9jdW1lbnQgZml0cyB0aGUgZm9sbG93aW5nOiA8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyI+MS4gVG8gdW5kZXJ0YWtlIHNjZW5hcmlvIGRlc2NyaXB0aW9ucywgaW5jbHVkaW5nIGRv
Y3VtZW50YXRpb24gb2YNCjxicj4NCmN1cnJlbnQgY2FwYWJpbGl0eSBpbnZlbnRvcmllcyBhbmQg
ZXhpc3RpbmcgQkNQcywgZm9yIGVudGVycHJpc2UgPGJyPg0KbmV0d29ya3MsIGluY2x1ZGluZyBt
YW5hZ2VkIGFuZCB1bm1hbmFnZWQgZWxlbWVudHMuIFRoZXNlIHRleHRzIHNob3VsZCA8YnI+DQpj
b250cmlidXRlIHRvd2FyZHMgYSBnYXAgYW5hbHlzaXMgYW5kIHByb3ZpZGUgYW4gYWdyZWVkIGJh
c2lzIGZvciA8YnI+DQpzdWJzZXF1ZW50IFdHIHJlY2hhcnRlcmluZyB0b3dhcmRzIGRldmVsb3Bt
ZW50IG9mIHNvbHV0aW9ucyAod2hpY2ggbWF5IDxicj4NCmJlIG1vcmUgYXBwcm9wcmlhdGUgZm9y
IG90aGVyIFdHcyB0byB1bmRlcnRha2UpIGFuZCBpbXByb3ZlZCBwcmFjdGljZXMuIDxicj4NCk9w
ZXJhdG9yIGlucHV0IHdpbGwgYmUgb2YgaGlnaCB2YWx1ZSBmb3IgdGhpcyB0ZXh0LiA8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+
UmVhZGluZyB0aGlzIHJlYWRpbmcsIEkgYXNrZWQgbXlzZWxmOiB3aGF0IGlzIHRoZSBzcGVjaWZp
YyBzY29wZSBvZiB0aGlzIGRvY3VtZW50PyBJIHNlZSBhIG1peCBvZiBzY2VuYXJpb3MsIGxpc3Rp
bmcgb2YgdGhlIGV4aXN0aW5nIHNvbHV0aW9ucywgYmVzdCBjdXJyZW50IHByYWN0aWNlcywgZXRj
Li4uIGFuZCBJJ20gd29uZGVyaW5nIHdoZXJlIHRoaXMgZG9jdW1lbnQgZml0cw0KIGluIGFsbCB0
aGUgSVB2NiBkb2N1bWVudHMgcmVudW1iZXJpbmcgZG9jdW1lbnRzOiBSRkMgNTg4NywgdGhpcyBk
b2N1bWVudCwgRW50ZXJwcmlzZSBJUHY2IERlcGxveW1lbnQgR3VpZGVsaW5lcyBkcmFmdC1pZXRm
LXY2b3BzLWVudGVycHJpc2UtaW5jcmVtZW50YWwtaXB2Ni0wMSwgcmZjNDE5MiwgZXRjLi4uDQo8
YnI+DQpCeSAmcXVvdDtldGMmcXVvdDssIEkgbWVhbiBzZWFyY2hpbmcgZm9yICZxdW90O3JlbnVt
JnF1b3Q7IGluIDxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL2Rvd25sb2FkL3JmYy1pbmRl
eC50eHQiPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvZG93bmxvYWQvcmZjLWluZGV4LnR4dDwvYT4u
PGJyPg0KSXQgc2VlbXMgdGhhdCBtYW55IG9mIHRoZXNlIGRvY3VtZW50cyBoYXZlIHRoZSBzYW1l
IHR5cGUgb2YgY29udGVudC4gVG9vIG1hbnkgYWN0dWFsbHkuIERvbid0IGdldCBtZSB3cm9uZywg
dGhlcmUgaXMgZ29vZCB0ZXh0IGluIHRoaXMgZG9jdW1lbnQuPGJyPg0KPGJyPg0KQm90dG9tIGxp
bmU6IGlmIHNvbWVvbmUgaXMgaW50ZXJlc3RlZCBpbiByZW51bWJlcmluZywgd2hhdCBpcyB0aGUg
b3JkZXJlZCBsaXN0IG9mIGRvY3VtZW50cyB0byBiZSByZWFkLCB3aXRoIHRoZSByZXNwZWN0aXZl
IGNvbnRlbnQuIE15IGNvbmNsdXNpb24gaXMgdGhhdCB0aGVyZSB3aWxsIGJlIGEgbG90IG9mIG92
ZXJsYXAuIEkgd291bGQgaGFwcHkgdG8gc3RhbmQgY29ycmVjdGVkLjxicj4NCjxicj4NCkJ0dywg
dGhpcyBkb2N1bWVudCB0aXRsZSBtZW50aW9ucyAmcXVvdDtndWlkZWxpbmVzJnF1b3Q7LCB3aGls
ZSBCQ1AgaXMgbWVudGlvbmVkIGFsbCBvdmVyLiA8YnI+DQo8YnI+DQpOb3RlOiBJIGRpZCBteSBo
b21lIHRyeWluZyB0byBmaW5kIHRoZSBhbnN3ZXI6IHJlYWQgUkZDIDU4ODcsIGxpc3RlbmVkIHRv
IHRoZSBJRVRGIDg1IG1lZXRpbmcgcmVjb3JkaW5nLCBldGMuLi48YnI+DQo8YnI+DQo8YnI+DQot
IEEgc2lkZSBub3RlIXF1ZXN0aW9uLCBhbmQgSSdtIG5vdCBzdXJlIGl0IGhhcyB0byBiZSBhZGRy
ZXNzZWQgYnkgdGhpcyBkcmFmdCwgYnV0IG9uZSBkYXksIEkgd291bGQgbGlrZSB0byBmaW5kIGFu
IGFuc3dlci48YnI+DQpIb3cgZG9lcyBhIE5NUyBkbyBhIGRpc2NvdmVyeSBvZiBhIHB1cmUgSVB2
NiBuZXR3b3JrPyBXaXRoIHNvbWV0aGluZyBiZXR0ZXIgdGhhbiBwaW5nIHN3ZWVwIG9idmlvdXNs
eS4uLjxicj4NCjxicj4NCjxicj4NCjx1PkVkaXRvcmlhbDwvdT48YnI+DQoxLjxicj4NClNlY3Rp
b24gMSwgcGFyYWdyYXBoIDE8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cHJlPjxzcGFuIGxhbmc9
IkVOLVVTIj4mbmJzcDsmbmJzcDsgUEkgc3BhY2UgaXMgbm90IGFsd2F5cyBhdmFpbGFibGU8bzpw
PjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOyZuYnNw
OyBmb3IgZW50ZXJwcmlzZXMgVGhlcmVmb3JlLCBpdCBpcyBkZXNpcmFibGUgdG8gZGV2ZWxvcCBt
ZWNoYW5pc21zIHRoYXQ8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0i
RU4tVVMiPiZuYnNwOyZuYnNwOyBzaW1wbGlmeSBJUHY2IHJlbnVtYmVyaW5nLjxvOnA+PC9vOnA+
PC9zcGFuPjwvcHJlPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPk1p
c3NpbmcgYSAmcXVvdDsuJnF1b3Q7PGJyPg0KPGJyPg0KMi48YnI+DQpTZWN0aW9uIDEsIHBhcmFn
cmFwaCAxPG86cD48L286cD48L3NwYW4+PC9wPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyI+Jm5i
c3A7Jm5ic3A7IEhvd2V2ZXIsIHdpZGVzcHJlYWQgdXNlIG9mIFBJIG1pZ2h0PG86cD48L286cD48
L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDsmbmJzcDsgY3JlYXRl
IHNlcmlvdXMgQkdQNCBzY2FsaW5nIHByb2JsZW1zIDxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBs
YW5nPSJFTi1VUyI+QSByZWZlcmVuY2UsIG9yIGEgc21hbGwgZXhwbGFuYXRpb24sIHdvdWxkIGJl
IHdlbGNvbWU8YnI+DQo8YnI+DQpSZWdhcmRzLCBCZW5vaXQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBw
dCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4N
Cg==

--_000_5D36713D8A4E7348A7E10DF7437A4B9239FD4003szxeml545mbschi_--

From internet-drafts@ietf.org  Wed Dec 12 01:22:27 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8824221F87A3; Wed, 12 Dec 2012 01:22:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.533
X-Spam-Level: 
X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ygmRr3rR-tu2; Wed, 12 Dec 2012 01:22:23 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37A3521F897C; Wed, 12 Dec 2012 01:22:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.36
Message-ID: <20121212092223.2559.38321.idtracker@ietfa.amsl.com>
Date: Wed, 12 Dec 2012 01:22:23 -0800
Cc: renum@ietf.org
Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-05.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 09:22:27 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Site Renumbering Working Group of th=
e IETF.

	Title           : IPv6 Site Renumbering Gap Analysis
	Author(s)       : Bing Liu
                          Sheng Jiang
                          Brian Carpenter
                          Stig Venaas
                          Wesley George
	Filename        : draft-ietf-6renum-gap-analysis-05.txt
	Pages           : 21
	Date            : 2012-12-12

Abstract:
   This document briefly introduces the existing mechanisms that could
   be utilized for IPv6 site renumbering and tries to cover most of the
   explicit issues and requirements of IPv6 renumbering. Through the gap
   analysis, the document provides a basis for future works that
   identify and develop solutions or to stimulate such development as
   appropriate. The gap analysis is presented following a renumbering
   event procedure summary.




The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-gap-analysis-05


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From leo.liubing@huawei.com  Wed Dec 12 01:31:07 2012
Return-Path: <leo.liubing@huawei.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 667D821F898A for <renum@ietfa.amsl.com>; Wed, 12 Dec 2012 01:31:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VYuGviHMKBp6 for <renum@ietfa.amsl.com>; Wed, 12 Dec 2012 01:31:06 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5A6E121F8989 for <renum@ietf.org>; Wed, 12 Dec 2012 01:31:06 -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.5-GA FastPath queued) with ESMTP id ANT47064; Wed, 12 Dec 2012 09:31:05 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 12 Dec 2012 09:30:19 +0000
Received: from SZXEML461-HUB.china.huawei.com (10.82.67.204) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 12 Dec 2012 09:31:04 +0000
Received: from SZXEML509-MBX.china.huawei.com ([10.82.67.37]) by szxeml461-hub.china.huawei.com ([10.82.67.204]) with mapi id 14.01.0323.003; Wed, 12 Dec 2012 17:30:35 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "renum@ietf.org" <renum@ietf.org>
Thread-Topic: [renum] I-D Action: draft-ietf-6renum-gap-analysis-05.txt
Thread-Index: AQHN2EptNDDghsXLc0yMGd6s/UyIiJgU5RnA
Date: Wed, 12 Dec 2012 09:30:34 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453CCFDA58@szxeml509-mbx>
References: <20121212092223.2559.38321.idtracker@ietfa.amsl.com>
In-Reply-To: <20121212092223.2559.38321.idtracker@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.144]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [renum] I-D Action: draft-ietf-6renum-gap-analysis-05.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 09:31:07 -0000

Hi, all

The gap draft was updated to address the issues raised during WGLC. Main pr=
ogress:
1. Raised discussion of "Parameterized IP-Specific Configurations" in the m=
ailing list to address the issues raised in Atlanta, seems they were fine w=
ith the expression, no oppositions.
2. Added a brief section 9.3 to reflect the open questions in draft-ietf-6r=
enum-static-problem

The authors think the draft is mature enough to move forward. Any comments =
please feel free to post.

Best regards,
Bing

> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> Of internet-drafts@ietf.org
> Sent: Wednesday, December 12, 2012 5:22 PM
> To: i-d-announce@ietf.org
> Cc: renum@ietf.org
> Subject: [renum] I-D Action: draft-ietf-6renum-gap-analysis-05.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the IPv6 Site Renumbering Working Group of =
the
> IETF.
>=20
> 	Title           : IPv6 Site Renumbering Gap Analysis
> 	Author(s)       : Bing Liu
>                           Sheng Jiang
>                           Brian Carpenter
>                           Stig Venaas
>                           Wesley George
> 	Filename        : draft-ietf-6renum-gap-analysis-05.txt
> 	Pages           : 21
> 	Date            : 2012-12-12
>=20
> Abstract:
>    This document briefly introduces the existing mechanisms that could
>    be utilized for IPv6 site renumbering and tries to cover most of the
>    explicit issues and requirements of IPv6 renumbering. Through the gap
>    analysis, the document provides a basis for future works that
>    identify and develop solutions or to stimulate such development as
>    appropriate. The gap analysis is presented following a renumbering
>    event procedure summary.
>=20
>=20
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6renum-gap-analysis
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-05
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-gap-analysis-05
>=20
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

From brian.e.carpenter@gmail.com  Wed Dec 12 02:57:24 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D674121F852D for <renum@ietfa.amsl.com>; Wed, 12 Dec 2012 02:57:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.355
X-Spam-Level: 
X-Spam-Status: No, score=-101.355 tagged_above=-999 required=5 tests=[AWL=-0.264, BAYES_00=-2.599, J_CHICKENPOX_48=0.6, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uPosYBOeqJbW for <renum@ietfa.amsl.com>; Wed, 12 Dec 2012 02:57:24 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8127521F89A3 for <renum@ietf.org>; Wed, 12 Dec 2012 02:57:23 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so332200eek.31 for <renum@ietf.org>; Wed, 12 Dec 2012 02:57:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=yhvhLZ69peYOHBv2TQUmlvlqxbQQATH5HXFvjqbzuC0=; b=B+goty7vpmRDaI1gPGAirTkpNWbPeLEMA73qrOOT48GuSn7KVQjlsj2FeRDwxIWh5s zpXeCw7M3vdQixM8LB25TltexiO6QVG2rqOiy4zhwTWSykX8SFm1Dyg/pzjTi9z+zQO1 7Dxl2WxChUeLqK+gdLGMTHa38aL2NXjUEwS6XQOqHs5mOJVxwIloSn/+Rt0vgTqy1Y94 8Hj4C8wqqRI1RIOqql2EtQpoL0mmH+5j7yqy5XrYCu11KmGe3ACe+iZkorU+Jz7eJpDq fQB1BLZyto0EoClvB1f0C07T9lxK3pM2O4tzZLecNY7uKs+I+K5n7kiMpC7ln+FJMm0i WQ5Q==
Received: by 10.14.207.6 with SMTP id m6mr1804485eeo.10.1355309842744; Wed, 12 Dec 2012 02:57:22 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-7.as13285.net. [2.102.219.7]) by mx.google.com with ESMTPS id r1sm55206718eeo.2.2012.12.12.02.57.20 (version=SSLv3 cipher=OTHER); Wed, 12 Dec 2012 02:57:21 -0800 (PST)
Message-ID: <50C8632C.2060501@gmail.com>
Date: Wed, 12 Dec 2012 10:57:48 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>
References: <50C73F18.5000408@cisco.com> <50C76C38.9000103@cisco.com>
In-Reply-To: <50C76C38.9000103@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: renum@ietf.org
Subject: Re: [renum] draft-ietf-6renum-enterprise: review
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 10:57:25 -0000

Benoit,

Here are my *personal* comments on your question. My co-authors may have
a different opinion!

On 11/12/2012 17:24, Benoit Claise wrote:
> Dear all,
> 
> I've been reviewing draft-ietf-6renum-enterprise
> 
> I have a concern with this document. Not really an objection in the form
> of a DISCUSS, but ...
> From the charter, I believe that this document fits the following:
> 
>    1. To undertake scenario descriptions, including documentation of
>    current capability inventories and existing BCPs, for enterprise
>    networks, including managed and unmanaged elements. These texts should
>    contribute towards a gap analysis and provide an agreed basis for
>    subsequent WG rechartering towards development of solutions (which may
>    be more appropriate for other WGs to undertake) and improved practices.
>    Operator input will be of high value for this text.
> 
> Reading this reading, I asked myself: what is the specific scope of this
> document? I see a mix of scenarios, listing of the existing solutions,
> best current practices, etc... and I'm wondering where this document
> fits in all the IPv6 documents renumbering documents: RFC 5887, this
> document, Enterprise IPv6 Deployment Guidelines
> draft-ietf-v6ops-enterprise-incremental-ipv6-01, rfc4192, etc...
> By "etc", I mean searching for "renum" in
> https://www.ietf.org/download/rfc-index.txt.
> It seems that many of these documents have the same type of content. Too
> many actually. Don't get me wrong, there is good text in this document.
> 
> Bottom line: if someone is interested in renumbering, what is the
> ordered list of documents to be read, with the respective content. My
> conclusion is that there will be a lot of overlap. I would happy to
> stand corrected.

This is a tricky point. RFC 5887 could probably never have been developed
by a WG - in fact it was a non-IAB revisit of an IAB document (RFC 1900).
And it succeeded, because 6renum was chartered. But 6renum was not
chartered to design solutions or even to write a cookbook. I believe
that the nature of the present draft is only to describe the situation
and the existing tools.

At some point the IESG will be given draft-ietf-6renum-gap-analysis
which "briefly introduces the existing mechanisms that could
be utilized for IPv6 site renumbering and tries to cover most of the
explicit issues and requirements of IPv6 renumbering. Through the gap
analysis, the document provides a basis for future works..."

I think that the whole picture will be clearer then - and the IESG
will hopefully decide which of the gaps require IETF action.

draft-carpenter-6renum-next-steps-00 may also help to answer
your question.

> Btw, this document title mentions "guidelines", while BCP is mentioned
> all over.

I'm wondering whether the title is a bit misleading. We discuss (best)
current practice but the real objective is preparation for the gap
analysis.

> 
> Note: I did my home trying to find the answer: read RFC 5887, listened
> to the IETF 85 meeting recording, etc...
> 
> 
> - A side note!question, and I'm not sure it has to be addressed by this
> draft, but one day, I would like to find an answer.
> How does a NMS do a discovery of a pure IPv6 network? With something
> better than ping sweep obviously...

Good question!

> _Editorial_

Noted for the next version.

   Brian

> 1.
> Section 1, paragraph 1
> 
>    PI space is not always available
>    for enterprises Therefore, it is desirable to develop mechanisms that
>    simplify IPv6 renumbering.
> 
> Missing a "."
> 
> 2.
> Section 1, paragraph 1
> 
>    However, widespread use of PI might
>    create serious BGP4 scaling problems
> 
> A reference, or a small explanation, would be welcome
> 
> Regards, Benoit
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

From sm@elandsys.com  Wed Dec 12 04:18:55 2012
Return-Path: <sm@elandsys.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9380621F8884 for <renum@ietfa.amsl.com>; Wed, 12 Dec 2012 04:18:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SBQXUYhqh4it for <renum@ietfa.amsl.com>; Wed, 12 Dec 2012 04:18:54 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B934F21F8868 for <renum@ietf.org>; Wed, 12 Dec 2012 04:18:54 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.142.100]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qBCCHQMt019247 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Dec 2012 04:17:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1355314661; bh=4XweF8dYE3mozLz9d4QzOPu82n1YMexYPiPR8muPVG8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4h3s00HYUb3rC3IxvDh/hv3QCKEpjskEMY1QYMEW5fp94om7jl9q6I2zTowVeaTWr DBVHi84w6xzgZdMAIZQzHA2AJqzIS8suaV9tBunVjHjTbJWqtJnwoyAB1koSDL4CfU ftHG/USAVUSMfCtEtDEWm2Toc0cxGg7YWV6SQ04k=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1355314661; i=@elandsys.com; bh=4XweF8dYE3mozLz9d4QzOPu82n1YMexYPiPR8muPVG8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1veFtrImuZ9q8eNSElcAvM+p8JCvSgsD5nPtlkPHMxVxN2xBIMgZmWjG1Bhtf3PZG LmNLWhErcZ1j5qU25SPAmo+7XLqOIokdsz8LA6gCklNluqmnGSm5+Ec6d8eoIn5+t0 S3jXq3gi59HVpSXbL+WlRDtPQf03+XOwNzEA5CDM=
Message-Id: <6.2.5.6.2.20121212020058.09352a08@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 12 Dec 2012 04:16:20 -0800
To: renum@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B9239FD4003@szxeml545-mbs.chi na.huawei.com>
References: <50C73F18.5000408@cisco.com> <50C76C38.9000103@cisco.com> <2CF4CB03E2AA464BA0982EC92A02CE2501DCE108@BY2PRD0512MB653.namprd05.prod.outlook.com> <5D36713D8A4E7348A7E10DF7437A4B9239FD4003@szxeml545-mbs.china.huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [renum] draft-ietf-6renum-enterprise: review
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 12:18:55 -0000

At 00:55 12-12-2012, Sheng Jiang wrote:
>For overlapping, yes, there are many document mentioned renumbering, 
>only because it is a common issue. Different from other documents 
>that mention renumbering as a minor relevant consideration, the 
>6renum-enterprise is dedicated for renumbering issue. It focuses on 
>enterprise scenarios and makes a comprehensive analysis, which is 
>not provided by the other documents.

I reviewed draft-ietf-6renum-enterprise-04 (see 
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg08511.html 
).  RFC 4192 and RFC 5887 are more informative than the draft.  I 
read the other 6renum drafts (which are not normative in this draft) 
to try to get a better idea of the subject the working group is 
trying to address.  I don't think that the analysis in this draft 
would be that helpful to enterprises.  The bottom line, in my humble 
opinion, is that it will not help IPv6 deployment significantly.

The 6renum charter says:

    "The task of the 6RENUM working group is to document existing renumbering
     practices for enterprise site networks and to identify specific
     renumbering problems or 'gaps' in the context of partial or site-wide
     renumbering."

In Section 1, it is mentioned that best renumbering practices are 
introduced.  That's at odds with the charter.

In Section 4, the paragraph for DNS starts with a reference to RFC 
2874.  The draft then has to explain that A6 RRs are not 
recommended.  If I am not mistaken there is only one line about ACLs 
in the draft.  That's the part which breaks stuff.  I would pay 
attention to ACLs as it can have a more significant impact than 
forgetting about DNS changes.

Regards,
S. Moonesamy 


From brian.e.carpenter@gmail.com  Wed Dec 12 06:49:20 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49E5321F8A3E for <renum@ietfa.amsl.com>; Wed, 12 Dec 2012 06:49:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.613
X-Spam-Level: 
X-Spam-Status: No, score=-101.613 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Peg-tj+sNBBb for <renum@ietfa.amsl.com>; Wed, 12 Dec 2012 06:49:19 -0800 (PST)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7D5E121F8903 for <renum@ietf.org>; Wed, 12 Dec 2012 06:49:19 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id a1so266771eaa.31 for <renum@ietf.org>; Wed, 12 Dec 2012 06:49:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=AgG5U6DmsuHfmD2Ic9qc9czHMeR+BR83X/vJgD/Gkdw=; b=QYrdWqwY3BgfFxPMzUCa8VZNYvWpTuX5/9V95EdahJb4qGZjwz95k1DgFMcO+cuKa0 QxMTjDO0CFIq5XUsFib6mO7QfT/F0lqLLMpa8ew/f7CJG0on2zPOl/yATyM/7G7e4et3 up/JK+9zYnq1M/Rcw6vlcJXKM47Q2wENN9YQMeV3PBvj/g9uVA37R3QLuUcyzXNGUmXv uzOe7K+el0zQI6YZn1zp5qk6/QiuGetFptAszeFY0UanBX4NHlaa3zYe5QSwkNqM6nX1 GF3VanBynBedPhqHZeNMiAsVF5i8ygiddbUPqZ2Enl7p6uqK/ugVKEMAPTlcurhXgctO f6aQ==
Received: by 10.14.219.72 with SMTP id l48mr3411948eep.37.1355323758751; Wed, 12 Dec 2012 06:49:18 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-7.as13285.net. [2.102.219.7]) by mx.google.com with ESMTPS id z8sm56362242eeo.11.2012.12.12.06.49.16 (version=SSLv3 cipher=OTHER); Wed, 12 Dec 2012 06:49:17 -0800 (PST)
Message-ID: <50C8998A.4060204@gmail.com>
Date: Wed, 12 Dec 2012 14:49:46 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
References: <50C73F18.5000408@cisco.com> <50C76C38.9000103@cisco.com>	<2CF4CB03E2AA464BA0982EC92A02CE2501DCE108@BY2PRD0512MB653.namprd05.prod.outlook.com>	<5D36713D8A4E7348A7E10DF7437A4B9239FD4003@szxeml545-mbs.china.huawei.com> <6.2.5.6.2.20121212020058.09352a08@resistor.net>
In-Reply-To: <6.2.5.6.2.20121212020058.09352a08@resistor.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: renum@ietf.org
Subject: Re: [renum] draft-ietf-6renum-enterprise: review
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 14:49:20 -0000

On 12/12/2012 12:16, S Moonesamy wrote:
> At 00:55 12-12-2012, Sheng Jiang wrote:
>> For overlapping, yes, there are many document mentioned renumbering,
>> only because it is a common issue. Different from other documents that
>> mention renumbering as a minor relevant consideration, the
>> 6renum-enterprise is dedicated for renumbering issue. It focuses on
>> enterprise scenarios and makes a comprehensive analysis, which is not
>> provided by the other documents.
> 
> I reviewed draft-ietf-6renum-enterprise-04 (see
> http://www.ietf.org/mail-archive/web/apps-discuss/current/msg08511.html
> ).  RFC 4192 and RFC 5887 are more informative than the draft.  I read
> the other 6renum drafts (which are not normative in this draft) to try
> to get a better idea of the subject the working group is trying to
> address.  I don't think that the analysis in this draft would be that
> helpful to enterprises.  

Actually, that isn't the intention. Analysis is not the same thing
as a solution. I think we need to change the title and Introduction a bit
to make this more clear.

> The bottom line, in my humble opinion, is that
> it will not help IPv6 deployment significantly.

What it helps is to document how we derived the gap analysis (coming
soon, it has not yet left the WG). Then the gap analysis will drive
whatever specification or BCP work needs to be done.

> The 6renum charter says:
> 
>    "The task of the 6RENUM working group is to document existing
> renumbering
>     practices for enterprise site networks and to identify specific
>     renumbering problems or 'gaps' in the context of partial or site-wide
>     renumbering."
> 
> In Section 1, it is mentioned that best renumbering practices are
> introduced.  That's at odds with the charter.

Well, in the sense that we imply a judgment, perhaps, but is it really
useful to delete the word "best"?

> In Section 4, the paragraph for DNS starts with a reference to RFC
> 2874.  The draft then has to explain that A6 RRs are not recommended. 

Yes, because one of the main reasons A6 was proposed was to assist
renumbering. The main reason that RFC 6563 was published this year
is that 6renum noticed that RFC 2874 was not marked "Historic"
and was still confusing some people.

> If I am not mistaken there is only one line about ACLs in the draft. 
> That's the part which breaks stuff.  I would pay attention to ACLs as it
> can have a more significant impact than forgetting about DNS changes.

Why? Are application programmers coding IPv6 addresses into their
applications instead of using FQDNs?

Of course ACLs are important, and we have been reminded by another
reviewer that they should be mentioned in draft-ietf-6renum-static-problem
too. But what more is there to say than "they need to be updated"?
New mechanisms are out of scope in this draft.

    Brian

> 
> Regards,
> S. Moonesamy
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum
> 

From sm@elandsys.com  Wed Dec 12 08:35:20 2012
Return-Path: <sm@elandsys.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B1E821F88C4 for <renum@ietfa.amsl.com>; Wed, 12 Dec 2012 08:35:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AhuUJvdCZHgY for <renum@ietfa.amsl.com>; Wed, 12 Dec 2012 08:35:19 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EEEE121F88C8 for <renum@ietf.org>; Wed, 12 Dec 2012 08:35:18 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.129.149]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qBCGYwMW021830 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Dec 2012 08:35:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1355330112; bh=CZVvnql9nfZc9AUoppSlJ7krSscHuMbCGMczu+aUNJ0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=uIPt1b8IVtRapvIj/hh+lls8sDnY46TC8cxgqbBRfQ6YRL38/jwMUdumUEtPFbSxW GIMlNGJOZdyyUCsysfyAydc651+PbJrZiOp15Vp/sY3CIfAPQmDidmBMFp7NCmA6zc zaUquNbaD2gOCicucZgews0M4mf8yS69CkAFijqQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1355330112; i=@elandsys.com; bh=CZVvnql9nfZc9AUoppSlJ7krSscHuMbCGMczu+aUNJ0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=jK5ZsMCvVrkG03467l6aXryp4XZWusGg8otD87NKGuYOg9E58OdB/k55oaPQkT03u dOQgWtbOA7gr9tf1qujaQtkRO2VI6km9ZpJNIOS2nAZkNCM5z8Iam8lOc2PlilyTxQ L5qlS9o8OO/ysXRXaLj/em0WHIoc3wjrIPB72El0=
Message-Id: <6.2.5.6.2.20121212070426.0aa016f8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 12 Dec 2012 08:14:51 -0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <50C8998A.4060204@gmail.com>
References: <50C73F18.5000408@cisco.com> <50C76C38.9000103@cisco.com> <2CF4CB03E2AA464BA0982EC92A02CE2501DCE108@BY2PRD0512MB653.namprd05.prod.outlook.com> <5D36713D8A4E7348A7E10DF7437A4B9239FD4003@szxeml545-mbs.china.huawei.com> <6.2.5.6.2.20121212020058.09352a08@resistor.net> <50C8998A.4060204@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: renum@ietf.org
Subject: Re: [renum] draft-ietf-6renum-enterprise: review
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 16:35:20 -0000

Hi Brian,
At 06:49 12-12-2012, Brian E Carpenter wrote:
>Actually, that isn't the intention. Analysis is not the same thing
>as a solution. I think we need to change the title and Introduction a bit
>to make this more clear.

That would help.  I was confused about what the document was about as 
it mentions guidelines and best practices.

>What it helps is to document how we derived the gap analysis (coming
>soon, it has not yet left the WG). Then the gap analysis will drive
>whatever specification or BCP work needs to be done.

The above makes matters clearer.  From Section 4:

   "This section recommends some solutions or strategies for the
    enterprise renumbering, chosen among existing mechanisms."

Section 4 comes out as recommendations about Best Current Practices.

>Well, in the sense that we imply a judgment, perhaps, but is it really
>useful to delete the word "best"?

I would describe it as existing practices or some wording around 
"best" if you would like to keep that word.  The above comments 
clarifies what the document is about.  I suggest having such an 
explanation in the document.

>Yes, because one of the main reasons A6 was proposed was to assist
>renumbering. The main reason that RFC 6563 was published this year
>is that 6renum noticed that RFC 2874 was not marked "Historic"
>and was still confusing some people.

I was confused about why RFC 2874 is being referenced.

 From Section 4.1:

    "It is recommended that the site have an automatic and systematic
     procedure for updating/synchronizing its DNS records, including
     both forward and reverse mapping [RFC2874].

The above makes a recommendation about DNS synchronization and refers 
to RFC 2874.  In the following paragraph it is mentioned that RFC 
2874 is not recommended.  I cannot recall off-hand a good reference 
for forward and reverse mapping.  I suggest removing the RFC 2874 
reference (see quoted text above).  The draft could keep things easy 
by also dropping the RFC 3364 reference and relying on RFC 6563 to 
explain why A6 RRs are no longer recommended.

>Why? Are application programmers coding IPv6 addresses into their
>applications instead of using FQDNs?

I hope that application programmers are not hard-coding IPv6 
addresses.  Section 4.1 mentions "system/network 
administrators".  Here is some text (from RFC 4038):

   "Many applications use IP addresses to identify network nodes and to
    establish connections to destination addresses."

I suggest using some variation of that text in the "Usage of FQDN" 
discussion.  The point is to explain that "it is a bad idea" and then 
say that using FQDNs avoids renumbering issues.

>Of course ACLs are important, and we have been reminded by another
>reviewer that they should be mentioned in draft-ietf-6renum-static-problem
>too. But what more is there to say than "they need to be updated"?
>New mechanisms are out of scope in this draft.

I misunderstood what the draft was about (see above).

Regards,
S. Moonesamy 


From sm@resistor.net  Thu Dec 13 14:30:48 2012
Return-Path: <sm@resistor.net>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6170721F8BC0; Thu, 13 Dec 2012 14:30:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.622
X-Spam-Level: 
X-Spam-Status: No, score=-102.622 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DuXb7kDugERN; Thu, 13 Dec 2012 14:30:47 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D20821F8B82; Thu, 13 Dec 2012 14:30:47 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qBDMUgEl002553; Thu, 13 Dec 2012 14:30:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1355437846; bh=WSEKHIqebEQnQgLCc6ZL0pFCt6KUn7xac63ccRMubsw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=VYBhfej1I/cuVVYqYKyHL3e9GQP4w9o13U0QqWMGT04NGgKOPDByK2iuIBaUtO+lW VBPZpCG9qfZ36Jd1dLQoiQoaYaoB7Ul4Y772W5emnuj2DPSynIRhlxnU+NGnuhQeK9 CX2GqqfhFK40P6zr8/CjH1GQWnn0nxudp4SCTXyI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1355437846; i=@resistor.net; bh=WSEKHIqebEQnQgLCc6ZL0pFCt6KUn7xac63ccRMubsw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OM+fWxWywv7Vxs3KW9meYKFMklyNTmyC7S0Tfvt0goATwV0Q/QSZiCHBPGLtAuZ4E h07ZEQoR6cNMWqqU47SPbRXvF9eI36nkRgG37okVjg5IQvxVHmVBxnCgSVMaBVFVVN FdS7P4Tp7uV0BkTHqOgNfuMtnIJCklUMf9XPSZco=
Message-Id: <6.2.5.6.2.20121213131533.0b7a65b0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 13 Dec 2012 14:22:45 -0800
To: renum@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <20121128152543.31789.28197.idtracker@ietfa.amsl.com>
References: <20121128152543.31789.28197.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: apps-discuss@ietf.org
Subject: Re: [renum] Last Call: <draft-ietf-6renum-static-problem-02.txt> (Problem Statement for Renumbering IPv6 Hosts with Static Addresses) to Informational RFC
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 22:30:48 -0000

At 07:25 28-11-2012, The IESG wrote:
>The IESG has received a request from the IPv6 Site Renumbering WG
>(6renum) to consider the following document:
>- 'Problem Statement for Renumbering IPv6 Hosts with Static Addresses'
>   <draft-ietf-6renum-static-problem-02.txt> as Informational RFC

These comments are after the Last Call.  As such I am ok if they are 
ignored.  There is a Cc to apps-discuss in case anyone is interested 
to comment about the application perspective.

I am aware that renumbering is difficult.  I have read about the 
claim that "addresses are stable over long periods of time" in RFC 
6250.  The Introduction Section of the draft mentions that:

   "Static addresses may be configured automatically, for example by
    stateful DHCPv6."

It's fine to assign IP addresses to printers through DHCPv6.  The 
printer is a one-function device and it usually isn't critical.  I 
wouldn't use DHCPv6 for servers to be on the safe side.  If I had to 
choose between walking to the server to be able to access it when 
things go wrong and pushing an IP configuration manually, I would 
choose the former as it would have a lower impact on service 
availability.  Note that the server may be running multiple services 
which could interact with each other.

In Section 2.3:

   "However, it is very widespread operational practice that servers have
    static IP addresses."

   "Such server addresses can be managed centrally even if they are
    static, by using DHCPv6 in stateful mode, and by generating both
    DHCPv6 data and DNS data from a common configuration database using a
    suitable configuration tool."

This draft argues for DHCPv6 as the solution to make renumbering 
easier.  The draft seems to focus more on the client perspective 
where DHCPv6 (or SLAAC) is a worthwhile alternative for address 
assignment.   There's more to a server than assigning an IP address 
to the host.  If I configure a "Listen" address for an application 
and there is a DNS failure, the application does not start.  The 
problem statement (Section 4) mentions among other things printers 
and desktops.  The server part relies on DHCPv6 and DNS for 
configuration management.  In my humble opinion, that's a recipe for 
service outage.

Regards,
-sm 


From brian.e.carpenter@gmail.com  Fri Dec 14 00:01:43 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 367C021F88DC; Fri, 14 Dec 2012 00:01:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.023
X-Spam-Level: 
X-Spam-Status: No, score=-101.023 tagged_above=-999 required=5 tests=[AWL=-0.502, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, TO_MALFORMED=1.17, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jxftuqW0qWnF; Fri, 14 Dec 2012 00:01:42 -0800 (PST)
Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by ietfa.amsl.com (Postfix) with ESMTP id 46B1A21F88DA; Fri, 14 Dec 2012 00:01:42 -0800 (PST)
Received: by mail-wg0-f46.google.com with SMTP id dr13so1252419wgb.13 for <multiple recipients>; Fri, 14 Dec 2012 00:01:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=TIgKsKTIqUFJomWM3TKaxPaS9SIhRqDonM5c74HUc98=; b=UZDlSSE/SjE86dqc+tyZ5EYd5cn7tg5+yKEeOXGKaLu0tSe9zZgRDSAJnf4RaPpqGv e4m+p4D8YsqbX+6BgXC4YbiW3C1H4fnNeGEog3vGOZkd7Kz1hZr0WWMrwzQR+ZboULIw rQ0A2P8KrtCl1Z7DjiiPjIjMANcnkpigFsxzGV02I0mHZzSLUyuDGCR+eG4rxkwnLvcF GUN7jiXzvwU4owDzmLBOZDHjf/2TMlCwdWOuttBFcpQmMiCFBA7RzfAXj0fnA1M1qu/p 0V33mR3P7thy+vBhomhtXh1SxATZqvKdRZCAwUaltgs7hm//FwCvxvLyksHtpn/wWGLj 2g1Q==
Received: by 10.180.99.227 with SMTP id et3mr1179231wib.6.1355472101107; Fri, 14 Dec 2012 00:01:41 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-217-46.as13285.net. [2.102.217.46]) by mx.google.com with ESMTPS id b1sm6396326wix.11.2012.12.14.00.01.38 (version=SSLv3 cipher=OTHER); Fri, 14 Dec 2012 00:01:40 -0800 (PST)
Message-ID: <50CADD05.1010207@gmail.com>
Date: Fri, 14 Dec 2012 08:02:13 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: sm@2001:470:f329:1::1.amsl.com
References: <20121128152543.31789.28197.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121213131533.0b7a65b0@resistor.net>
In-Reply-To: <6.2.5.6.2.20121213131533.0b7a65b0@resistor.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: renum@ietf.org, apps-discuss@ietf.org
Subject: Re: [renum] [apps-discuss] Last Call: <draft-ietf-6renum-static-problem-02.txt> (Problem Statement for Renumbering IPv6 Hosts with Static Addresses) to Informational RFC
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 08:01:43 -0000

> The server part relies on DHCPv6 and DNS for configuration management.  In my humble opinion, that's a recipe for service outage.

In my world, DHCP and DNS have been mission critical for twenty years.

Regards
   Brian Carpenter




On 13/12/2012 22:22, SM wrote:
> At 07:25 28-11-2012, The IESG wrote:
>> The IESG has received a request from the IPv6 Site Renumbering WG
>> (6renum) to consider the following document:
>> - 'Problem Statement for Renumbering IPv6 Hosts with Static Addresses'
>>   <draft-ietf-6renum-static-problem-02.txt> as Informational RFC
> 
> These comments are after the Last Call.  As such I am ok if they are
> ignored.  There is a Cc to apps-discuss in case anyone is interested to
> comment about the application perspective.
> 
> I am aware that renumbering is difficult.  I have read about the claim
> that "addresses are stable over long periods of time" in RFC 6250.  The
> Introduction Section of the draft mentions that:
> 
>   "Static addresses may be configured automatically, for example by
>    stateful DHCPv6."
> 
> It's fine to assign IP addresses to printers through DHCPv6.  The
> printer is a one-function device and it usually isn't critical.  I
> wouldn't use DHCPv6 for servers to be on the safe side.  If I had to
> choose between walking to the server to be able to access it when things
> go wrong and pushing an IP configuration manually, I would choose the
> former as it would have a lower impact on service availability.  Note
> that the server may be running multiple services which could interact
> with each other.
> 
> In Section 2.3:
> 
>   "However, it is very widespread operational practice that servers have
>    static IP addresses."
> 
>   "Such server addresses can be managed centrally even if they are
>    static, by using DHCPv6 in stateful mode, and by generating both
>    DHCPv6 data and DNS data from a common configuration database using a
>    suitable configuration tool."
> 
> This draft argues for DHCPv6 as the solution to make renumbering
> easier.  The draft seems to focus more on the client perspective where
> DHCPv6 (or SLAAC) is a worthwhile alternative for address assignment.  
> There's more to a server than assigning an IP address to the host.  If I
> configure a "Listen" address for an application and there is a DNS
> failure, the application does not start.  The problem statement (Section
> 4) mentions among other things printers and desktops.  The server part
> relies on DHCPv6 and DNS for configuration management.  In my humble
> opinion, that's a recipe for service outage.
> 
> Regards,
> -sm
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
> 

From internet-drafts@ietf.org  Fri Dec 21 00:57:01 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC04921F8A86; Fri, 21 Dec 2012 00:57:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WEU4oCDAJg3x; Fri, 21 Dec 2012 00:57:01 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43C6721F8A56; Fri, 21 Dec 2012 00:57:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20121221085701.6227.80317.idtracker@ietfa.amsl.com>
Date: Fri, 21 Dec 2012 00:57:01 -0800
Cc: renum@ietf.org
Subject: [renum] I-D Action: draft-ietf-6renum-enterprise-05.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 08:57:01 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Site Renumbering Working Group of th=
e IETF.

	Title           : IPv6 Enterprise Network Renumbering Scenarios, Considera=
tions and Methods
	Author(s)       : Sheng Jiang
                          Bing Liu
                          Brian Carpenter
	Filename        : draft-ietf-6renum-enterprise-05.txt
	Pages           : 17
	Date            : 2012-12-21

Abstract:
   This document analyzes events that cause renumbering and describes
   the current renumbering methods. These are described in three
   categories: those applicable during network design, those applicable
   during preparation for renumbering, and those applicable during the
   renumbering operation.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6renum-enterprise

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6renum-enterprise-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-enterprise-05


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From brian.e.carpenter@gmail.com  Fri Dec 21 05:53:58 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C60321F8B29 for <renum@ietfa.amsl.com>; Fri, 21 Dec 2012 05:53:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.604
X-Spam-Level: 
X-Spam-Status: No, score=-101.604 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UOMPgktBZSFl for <renum@ietfa.amsl.com>; Fri, 21 Dec 2012 05:53:58 -0800 (PST)
Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by ietfa.amsl.com (Postfix) with ESMTP id D4C3921F8775 for <renum@ietf.org>; Fri, 21 Dec 2012 05:53:57 -0800 (PST)
Received: by mail-wi0-f175.google.com with SMTP id hm11so5086043wib.8 for <renum@ietf.org>; Fri, 21 Dec 2012 05:53:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=f2DPHiIHubXQmoQh0BGjOfR1CUuc/uzqgSktfsil6XE=; b=GQYbNUbPXJCz0dR0O7wih4j7HHJncpjGsifwogKmPaLj5TkIpaDzI+gPnJ9LVZ2VCT h1Xwtgooe+7Qlyyvk8sU32uPLN3B92RGebfbDbRDi0N5lr3E2cvPZkbVWrONFsrUI9Z5 GRj3pJbnBHrAGllyDzrDziKEcyC0ygVHy4eWd29JXzbMTIcRiaTatpRYAQRRBq9D+Je8 Fcm+VtJdadmY2+O9webFujZmnMISeIMzR9tRx/JTwexkNcHxsZm2XeiNGWC57KJZoH0A /2ILK3sj88KBu0Jit72NMQP62wlc+YBhONcJThczJgNiuvZ1+q/mtmoyol+CsFNrbjOo 2z8A==
X-Received: by 10.180.101.99 with SMTP id ff3mr23281437wib.21.1356098037089; Fri, 21 Dec 2012 05:53:57 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-97.as13285.net. [2.102.219.97]) by mx.google.com with ESMTPS id df2sm20731094wib.0.2012.12.21.05.53.54 (version=SSLv3 cipher=OTHER); Fri, 21 Dec 2012 05:53:55 -0800 (PST)
Message-ID: <50D46A01.4000903@gmail.com>
Date: Fri, 21 Dec 2012 13:54:09 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: renum@ietf.org
References: <20121221085701.6227.80317.idtracker@ietfa.amsl.com>
In-Reply-To: <20121221085701.6227.80317.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [renum] I-D Action: draft-ietf-6renum-enterprise-05.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 13:53:59 -0000

WG,

This update is in response to Last Call and IESG comments. Here are a few notes:

Reacting to several reviewers, we clarified scope (analysis and description of
current methods) and reduced "BCP" language that confused the scope. Also
numerous editorial corrections.

Substantial reorganisation of the DNS section to improve logic and readability.

Apps Area review - clarified comments on application servers
and use of FQDN.

Martin Stiemerling's review - clarified discussion of black list
issue according to security area review.

OPS-DIR review -
 "[RFC4057] needs to be a Normative Reference" - not possible, it's an Informational RFC.

 "Have suggestions for verifying correct operation been discussed?" - paragraph added to
 section 4.3.

Benoit Claise's review - clarified scope, then

 "Section 1, paragraph 1

   However, widespread use of PI might
   create serious BGP4 scaling problems

 A reference, or a small explanation, would be welcome "

It's unfortunate that the RRG did not produce an RFC on BGP scaling problems.
We can refer to RFC 4116 but it isn't ideal.

SECDIR review - all points have been adopted

Regards
   Brian, Sheng, Bing


On 21/12/2012 08:57, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the IPv6 Site Renumbering Working Group of the IETF.
> 
> 	Title           : IPv6 Enterprise Network Renumbering Scenarios, Considerations and Methods
> 	Author(s)       : Sheng Jiang
>                           Bing Liu
>                           Brian Carpenter
> 	Filename        : draft-ietf-6renum-enterprise-05.txt
> 	Pages           : 17
> 	Date            : 2012-12-21
> 
> Abstract:
>    This document analyzes events that cause renumbering and describes
>    the current renumbering methods. These are described in three
>    categories: those applicable during network design, those applicable
>    during preparation for renumbering, and those applicable during the
>    renumbering operation.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6renum-enterprise
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6renum-enterprise-05
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-6renum-enterprise-05
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 

From wesley.george@twcable.com  Fri Dec 21 06:43:04 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44FFD21F84DC for <renum@ietfa.amsl.com>; Fri, 21 Dec 2012 06:43:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.566
X-Spam-Level: 
X-Spam-Status: No, score=-0.566 tagged_above=-999 required=5 tests=[AWL=-0.103, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7e3x3QicY-Fn for <renum@ietfa.amsl.com>; Fri, 21 Dec 2012 06:43:03 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 44CB621F85E8 for <renum@ietf.org>; Fri, 21 Dec 2012 06:43:02 -0800 (PST)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.84,329,1355115600";  d="scan'208";a="1824904"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 21 Dec 2012 09:42:35 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Fri, 21 Dec 2012 09:42:48 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "renum@ietf.org" <renum@ietf.org>
Date: Fri, 21 Dec 2012 09:42:55 -0500
Thread-Topic: [renum] I-D Action: draft-ietf-6renum-enterprise-05.txt
Thread-Index: Ac3fgrhWUs1duagESbCzvBeM0ufKIgABY2zg
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD5923033A5253EE@PRVPEXVS15.corp.twcable.com>
References: <20121221085701.6227.80317.idtracker@ietfa.amsl.com> <50D46A01.4000903@gmail.com>
In-Reply-To: <50D46A01.4000903@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [renum] I-D Action: draft-ietf-6renum-enterprise-05.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 14:43:04 -0000

> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf

> Benoit Claise's review - clarified scope, then
>
>  "Section 1, paragraph 1
>
>    However, widespread use of PI might
>    create serious BGP4 scaling problems
>
>  A reference, or a small explanation, would be welcome "
>
> It's unfortunate that the RRG did not produce an RFC on BGP scaling
> problems.
[WEG] They didn't? While RRG didn't come to consensus on a *solution*, ther=
e was consensus documented about several aspects of the problem space that =
should serve as the necessary level of background reading to support this a=
ssertion.

> We can refer to RFC 4116 but it isn't ideal.
[WEG]
You may find better reference points in RFC4984, 6227, or even 6115.

Wes George

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From brian.e.carpenter@gmail.com  Fri Dec 21 06:59:54 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23E0921F85ED for <renum@ietfa.amsl.com>; Fri, 21 Dec 2012 06:59:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.606
X-Spam-Level: 
X-Spam-Status: No, score=-101.606 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YMPTyxpC0KkQ for <renum@ietfa.amsl.com>; Fri, 21 Dec 2012 06:59:53 -0800 (PST)
Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by ietfa.amsl.com (Postfix) with ESMTP id 1248921F85E8 for <renum@ietf.org>; Fri, 21 Dec 2012 06:59:52 -0800 (PST)
Received: by mail-we0-f182.google.com with SMTP id u54so2265068wey.27 for <renum@ietf.org>; Fri, 21 Dec 2012 06:59:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=TXqwCN942I7Qu5FMGFNE1eH4sVlmb5RZxjazKahzcB0=; b=h940K846aEek997SPhC1Kl/wL/QDIh2Y1VyjaaoTXzaPXU8+nTJ3mAGl/SYEd4LQW6 4Tmh56iIG+o6TMaW3vYeKzz4nVzeZ8QRU5fgU3AxA6pdA5C2TW2tp0/opZnFbvJz6EIS QGYj/7IDrrkW+QErFzCUCju2abkX9WNJhnhDdnZ6wqKRgTRFM2i/OgrAb76J23XY5FSB ar09qQ6EZ8ZBkHAlJXNKzHBdQleyaI7CyTmhbk6lYdvhP+QEsaKHCIz8+49aQuN4+Wqd iSSmn23UKPLHZ3R/XszO082tR0FouiA77mXB2bGZfgNMjlct8az8JqyXsXWxITuK4aO6 pZVA==
X-Received: by 10.181.13.75 with SMTP id ew11mr23692878wid.9.1356101992074; Fri, 21 Dec 2012 06:59:52 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-97.as13285.net. [2.102.219.97]) by mx.google.com with ESMTPS id hg17sm30154416wib.1.2012.12.21.06.59.50 (version=SSLv3 cipher=OTHER); Fri, 21 Dec 2012 06:59:51 -0800 (PST)
Message-ID: <50D47975.7000002@gmail.com>
Date: Fri, 21 Dec 2012 15:00:05 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "George, Wes" <wesley.george@twcable.com>
References: <20121221085701.6227.80317.idtracker@ietfa.amsl.com> <50D46A01.4000903@gmail.com> <2671C6CDFBB59E47B64C10B3E0BD5923033A5253EE@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923033A5253EE@PRVPEXVS15.corp.twcable.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] I-D Action: draft-ietf-6renum-enterprise-05.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 14:59:54 -0000

Wes,

On 21/12/2012 14:42, George, Wes wrote:
>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> 
>> Benoit Claise's review - clarified scope, then
>>
>>  "Section 1, paragraph 1
>>
>>    However, widespread use of PI might
>>    create serious BGP4 scaling problems
>>
>>  A reference, or a small explanation, would be welcome "
>>
>> It's unfortunate that the RRG did not produce an RFC on BGP scaling
>> problems.
> [WEG] They didn't? While RRG didn't come to consensus on a *solution*, there was consensus documented about several aspects of the problem space that should serve as the necessary level of background reading to support this assertion.

Personally I wish that draft-narten-radir-problem-statement had
become an RFC. The published RRG documents say rather little about
the root causes of the scaling problem.

>> We can refer to RFC 4116 but it isn't ideal.
> [WEG]
> You may find better reference points in RFC4984, 6227, or even 6115.

I think that 6227 is the best of those for this purpose.

Thanks
    Brian

From Fred.L.Templin@boeing.com  Fri Dec 21 09:45:28 2012
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C68A321F86C0 for <renum@ietfa.amsl.com>; Fri, 21 Dec 2012 09:45:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iue8Cv0IEWfP for <renum@ietfa.amsl.com>; Fri, 21 Dec 2012 09:45:25 -0800 (PST)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 6D03A21F86A1 for <renum@ietf.org>; Fri, 21 Dec 2012 09:45:25 -0800 (PST)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id qBLHjOD7016113 for <renum@ietf.org>; Fri, 21 Dec 2012 09:45:24 -0800
Received: from XCH-NWHT-03.nw.nos.boeing.com (xch-nwht-03.nw.nos.boeing.com [130.247.71.23]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id qBLHjNtK016104 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 21 Dec 2012 09:45:23 -0800
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-03.nw.nos.boeing.com ([130.247.71.23]) with mapi; Fri, 21 Dec 2012 09:45:23 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "George, Wes" <wesley.george@twcable.com>
Date: Fri, 21 Dec 2012 09:45:19 -0800
Thread-Topic: [renum] I-D Action: draft-ietf-6renum-enterprise-05.txt
Thread-Index: Ac3fi+CvPr4bpRIGTzCaS2KKV0ozJAAFrixA
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65E0EE59ABD@XCH-NW-01V.nw.nos.boeing.com>
References: <20121221085701.6227.80317.idtracker@ietfa.amsl.com> <50D46A01.4000903@gmail.com> <2671C6CDFBB59E47B64C10B3E0BD5923033A5253EE@PRVPEXVS15.corp.twcable.com> <50D47975.7000002@gmail.com>
In-Reply-To: <50D47975.7000002@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: No
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] I-D Action: draft-ietf-6renum-enterprise-05.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 17:45:28 -0000

> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of
> Brian E Carpenter
> Sent: Friday, December 21, 2012 7:00 AM
> To: George, Wes
> Cc: renum@ietf.org
> Subject: Re: [renum] I-D Action: draft-ietf-6renum-enterprise-05.txt
>=20
> Wes,
>=20
> On 21/12/2012 14:42, George, Wes wrote:
> >> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> >
> >> Benoit Claise's review - clarified scope, then
> >>
> >>  "Section 1, paragraph 1
> >>
> >>    However, widespread use of PI might
> >>    create serious BGP4 scaling problems
> >>
> >>  A reference, or a small explanation, would be welcome "
> >>
> >> It's unfortunate that the RRG did not produce an RFC on BGP scaling
> >> problems.
> > [WEG] They didn't? While RRG didn't come to consensus on a *solution*,
> there was consensus documented about several aspects of the problem space
> that should serve as the necessary level of background reading to support
> this assertion.
>=20
> Personally I wish that draft-narten-radir-problem-statement had
> become an RFC. The published RRG documents say rather little about
> the root causes of the scaling problem.

Agree.

> >> We can refer to RFC 4116 but it isn't ideal.
> > [WEG]
> > You may find better reference points in RFC4984, 6227, or even 6115.
>=20
> I think that 6227 is the best of those for this purpose.

Also agree. IMHO, RFC6115 shows bias and was a snapsot-in-time
before all ideas were fully developed.

Thanks - Fred
fred.l.templin@boeing.com
=20
> Thanks
>     Brian
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum

From internet-drafts@ietf.org  Sun Dec 23 23:45:05 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE97421F8A74; Sun, 23 Dec 2012 23:45:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KPhVlS5ya+T2; Sun, 23 Dec 2012 23:44:46 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF34621F8A75; Sun, 23 Dec 2012 23:44:20 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20121224074420.1190.74267.idtracker@ietfa.amsl.com>
Date: Sun, 23 Dec 2012 23:44:20 -0800
Cc: renum@ietf.org
Subject: [renum] I-D Action: draft-ietf-6renum-static-problem-03.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Dec 2012 07:45:05 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Site Renumbering Working Group of th=
e IETF.

	Title           : Problem Statement for Renumbering IPv6 Hosts with Static=
 Addresses in Enterprise Networks
	Author(s)       : Brian Carpenter
                          Sheng Jiang
	Filename        : draft-ietf-6renum-static-problem-03.txt
	Pages           : 13
	Date            : 2012-12-23

Abstract:
   This document analyses the problems of updating the IPv6 addresses of
   hosts in enterprise networks that for operational reasons require
   static addresses.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6renum-static-problem

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6renum-static-problem-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-static-problem-03


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From brian.e.carpenter@gmail.com  Sun Dec 23 23:58:16 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AE0121F8BB3 for <renum@ietfa.amsl.com>; Sun, 23 Dec 2012 23:58:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.599
X-Spam-Level: 
X-Spam-Status: No, score=-101.599 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R02sVU54FKX1 for <renum@ietfa.amsl.com>; Sun, 23 Dec 2012 23:58:15 -0800 (PST)
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by ietfa.amsl.com (Postfix) with ESMTP id 699EF21F8B73 for <renum@ietf.org>; Sun, 23 Dec 2012 23:58:15 -0800 (PST)
Received: by mail-wi0-f180.google.com with SMTP id hj13so3890894wib.13 for <renum@ietf.org>; Sun, 23 Dec 2012 23:58:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=kyepBQ5ZJ4WTYmrhW4O25zaZMJXvXVswpZnVCaYQCkc=; b=yEDJ3JIOPc6HFaug9gOJMgIKswO59fSICeM/aYdIPQDj8e7R0O2GE0iTR/wURwXm2A ulpAtCokW+2XXbD5AIuXa4RmysrOOXMcXuic1XUuvIyVzcOFgUyGs+YLq3HAklOh3Wnq 2FnQqvt3s7U3gUhjCd9ZM7zm9KWYowg86tPizUPdL7gjmEq75GB5L6tTUxAQnGmVdk3Z U8b73izkO3U2RzZnwcQ0UX42pvDSKHHROHub8cKTRFO2gqHgTF6YpRoWxdOoLLqOPcHj CJgScsL8haZn9SydxSfe4L61vkXGQ3KXqmti08KB+f3QfFmFiSMghbdPlOMAag2sfbGs t1Ng==
X-Received: by 10.194.7.104 with SMTP id i8mr34270999wja.27.1356335894238; Sun, 23 Dec 2012 23:58:14 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-217-97.as13285.net. [2.102.217.97]) by mx.google.com with ESMTPS id bd6sm10605209wib.10.2012.12.23.23.58.11 (version=SSLv3 cipher=OTHER); Sun, 23 Dec 2012 23:58:12 -0800 (PST)
Message-ID: <50D80B11.60201@gmail.com>
Date: Mon, 24 Dec 2012 07:58:09 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: renum@ietf.org
References: <20121224074420.1190.74267.idtracker@ietfa.amsl.com>
In-Reply-To: <20121224074420.1190.74267.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qti.qualcomm.com>, Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [renum] I-D Action: draft-ietf-6renum-static-problem-03.txt
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Dec 2012 07:58:16 -0000

Hi 6renum WG and others,

This update is intended to deal with comments received during
IETF Last Call and IESG review.

The comments from Brian Haberman, Pete Resnick, and Adrian Farrel
were quite straightforward and have been dealt with. In particular,
the document scope was clarified and the discussion of Dynamic DNS
update has been corrected.

The review by Ralph Droms raised a number of points:

> > DNS, mDNS and SLP are mentioned in the context of name resolution.  Is
> > SLP deployed widely enough to warrant mention?

Lack of deployment is exactly the reason for mentioning it. The text
should make that clear now.

> > What about LLMNR and uPNP?

These are not IETF standards track protocols and don't seem to be aimed
at enterprise networks. However, we have modified the text to refer to
discovery protocols in general.

> > I don't understand why ULAs are identified as somehow affecting the
> > use or impact of static addresses.

Clarified the text.

> > DHCPv6 PD should be mentioned in the context of prefix assignment.

This is discussed in the more general document draft-ietf-6renum-enterprise.
It isn't specific to static addressing.

> > Is it really still common practice that "printers in particular are
> > manually assigned a fixed address (typically an [RFC1918] address) and
> > that users are told to manually configure printer access using that
> > fixed address"?

Unfortunately there are plenty of smaller sites that still do this (and many
that don't, of course).

> > In section 2.3, addresses assigned through DHCPv6 are considered
> > problematic because the address might expire, but later DHCPv6 is
> > suggested as a way of assigning addresses to solve renumbering of
> > static addresses.

Both things can be simultaneously valid; that's part of the renumbering
dilemma. Tuned the text to make it seem less paradoxical.

> > I don't understand the first sentence of 2.4.  Isn't the requirement
> > for a static address based on the need to maintain transport sessions
> > over VM movement (which isn't really how I understand the first
> > sentence).

Yes. This text has been updated for clarity.

> > In section 2.5, if asset management is based on MAC addresses, why are
> > static IP addresses an issue?
> >
> > I don't understand the connection between "If [...] a particular host
> > is found to be generating some form of unwanted traffic, it is urgent
> > to be able to track back from its IP address to its physical location"
> > and renumbering of static addressing.

There are indeed sites where IPv4 addresses are statically bound to
the MAC address but SLAAC is used for IPv6, with privacy addresses permitted.
But sites that choose to migrate IPv4 practices to IPv6 will probably bind
the MAC address and the IPv6 address. Surely the IETF can't tell them
not to do that?

> > In section 2.7, this claim may be true:
> >
> >   In any case, when network elements are renumbered, existing user
> >   sessions may not survive, because of temporary "destination
> >   unreachable" conditions being treated as fatal errors.  This aspect
> >   needs further investigation.
> >
> > but what is its connection to renumbering static addresses?

None in particular ;-). Deleted.

> > Section 2.8 makes a valid point about the relationship between static
> > addresses and asset management, but goes into solution space when it
> > talks about DHCPv6 for configuring static addresses.

Toned down the "should" language.

> > I don't understand the first paragraph of section 3.

Reworded.

> >   4.  If external prefix renumbering is required, the RFC 4192
> >       procedure is followed.
> >
> > What about renumbering required by strictly internal topology changes
> > in the network?  I.e., I think "external" can be dropped.

Agreed.

Regards
   Brian Carpenter
