
From tjc@ecs.soton.ac.uk  Mon Nov  5 08:01:07 2012
Return-Path: <tjc@ecs.soton.ac.uk>
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 C634321F8A9A for <renum@ietfa.amsl.com>; Mon,  5 Nov 2012 08:01:07 -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, HTML_MESSAGE=0.001]
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 CtH0Iob3IBQj for <renum@ietfa.amsl.com>; Mon,  5 Nov 2012 08:01:06 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 93AA821F89C7 for <renum@ietf.org>; Mon,  5 Nov 2012 08:01:06 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id qA5G11QA005834 for <renum@ietf.org>; Mon, 5 Nov 2012 16:01:01 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk qA5G11QA005834
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1352131261; bh=FHFXi23dS+bEIJQ7B1CRqpJno+8=; h=From:Subject:Date:To:Mime-Version:References; b=IY7mVEMMwZYtjF3HhAbHE4tATKf7nAL9Z5Af3wI7nXD43mE+Yw5gVkkdRzeFjRnf0 JHqGeemBelyhphT16+FyAMnAdNH6d36kBXZ987SSeE2DZmG/nUzsWV54/YlOOjkpME VmzuaxYRTlcg2rKFB+UC9jCOEdhAPrwjzvwbhVBU=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id oA4G110430657029JN ret-id none; Mon, 05 Nov 2012 16:01:01 +0000
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id qA5G0uT4020562 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Mon, 5 Nov 2012 16:00:57 GMT
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8BE7F5CE-6505-426E-8C89-94837A27D114"
Message-ID: <EMEW3|5dd49656908eede731432b250442b6bfoA4G1103tjc|ecs.soton.ac.uk|FC0D275D-9C24-424E-ABBA-FCC2B4E9A236@ecs.soton.ac.uk>
Date: Mon, 5 Nov 2012 16:00:56 +0000
To: "renum@ietf.org" <renum@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=oA4G11043065702900; tid=oA4G110430657029JN; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
References: <FC0D275D-9C24-424E-ABBA-FCC2B4E9A236@ecs.soton.ac.uk>
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: qA5G11QA005834
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: [renum] 6renum agenda
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, 05 Nov 2012 16:01:07 -0000

--Apple-Mail=_8BE7F5CE-6505-426E-8C89-94837A27D114
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

A reminder of our agenda later this week:
https://datatracker.ietf.org/meeting/85/agenda/6renum/

The aim is to confirm the wrap up of the WG, and where the followup work =
will be done.
=20
Fred has submitted a draft around his slot, see =
http://tools.ietf.org/html/draft-baker-6renum-oss-renumbering-00

Tim

IPv6 Site Renumbering (6renum) WG

THURSDAY, November 8, 2012
1730-1830  Afternoon Session III
Salon A
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D

* Administravia (5 mins)
  Note Well
  (Chairs)

* draft-ietf-6renum-gap-analysis-04 (10 mins)
  (Bing Liu)

* Next steps (30 mins)
  Inventory of protocol work to be undertaken elsewhere
  Confirmation of WG closure
  Open discussion
  (Brian Carpenter)

* Renumbering using an OSS (15 mins)
  (Fred Baker)=

--Apple-Mail=_8BE7F5CE-6505-426E-8C89-94837A27D114
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi,<div><br></div><div>A reminder of our agenda later this week:</div><div><a href="https://datatracker.ietf.org/meeting/85/agenda/6renum/">https://datatracker.ietf.org/meeting/85/agenda/6renum/</a></div><div><br></div><div>The aim is to confirm the wrap up of the WG, and where the followup work will be done.</div><div>&nbsp;</div><div>Fred has submitted a draft around his slot, see&nbsp;<a href="http://tools.ietf.org/html/draft-baker-6renum-oss-renumbering-00">http://tools.ietf.org/html/draft-baker-6renum-oss-renumbering-00</a></div><div><br></div><div>Tim</div><div><br></div><div><pre style="word-wrap: break-word; white-space: pre-wrap; ">IPv6 Site Renumbering (6renum) WG

THURSDAY, November 8, 2012
1730-1830  Afternoon Session III
Salon A
=====================================================

* Administravia (5 mins)
  Note Well
  (Chairs)

* draft-ietf-6renum-gap-analysis-04 (10 mins)
  (Bing Liu)

* Next steps (30 mins)
  Inventory of protocol work to be undertaken elsewhere
  Confirmation of WG closure
  Open discussion
  (Brian Carpenter)

* Renumbering using an OSS (15 mins)
  (Fred Baker)</pre></div></body></html>
--Apple-Mail=_8BE7F5CE-6505-426E-8C89-94837A27D114--

From brian.e.carpenter@gmail.com  Fri Nov  9 07:43:13 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 E799C21F860D for <renum@ietfa.amsl.com>; Fri,  9 Nov 2012 07:43:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.591
X-Spam-Level: 
X-Spam-Status: No, score=-103.591 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, 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 JhSZFZfLsdOd for <renum@ietfa.amsl.com>; Fri,  9 Nov 2012 07:43:13 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 15B5821F85C2 for <renum@ietf.org>; Fri,  9 Nov 2012 07:43:13 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id fb11so3073057pad.31 for <renum@ietf.org>; Fri, 09 Nov 2012 07:43:12 -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:content-type:content-transfer-encoding; bh=qRZgw96fDdyO7VqpbUYmW1Tkg5/27lXMG8g/jo4buQU=; b=NgcLB9YXQ+EkImcolY2uOpENzVrEvIIVvaJwG/c8VMjenHdF3K0sG788qQKO0I1MlH ZOcG0PRkmizoqNPD8H3UH6UszsrR4BL2CUktOldEcCIU27kbtUCXH1sU4fZ1TUGQgo29 SnA7UgvFpZrGornl2k7XVVArFd2KfpUid/U4son9D7VztJ+L8nQcxF/XhGuExi/IcppQ HgrwK+LU9+o4tUvxFIP9g+n8YCOJdB148C503lNcI3/FVU/qdfuqZMYTAl9qZC9RVREE xiywnVc4ZkpwSmWQMkWltFgWENvXItcckDWHAFG9nhsvmaba708551k0WRggatQf4BFk Uhiw==
Received: by 10.66.79.133 with SMTP id j5mr32472330pax.51.1352475792820; Fri, 09 Nov 2012 07:43:12 -0800 (PST)
Received: from [130.129.19.51] (dhcp-1333.meeting.ietf.org. [130.129.19.51]) by mx.google.com with ESMTPS id t1sm18121822paw.11.2012.11.09.07.43.11 (version=SSLv3 cipher=OTHER); Fri, 09 Nov 2012 07:43:11 -0800 (PST)
Message-ID: <509D249C.9070105@gmail.com>
Date: Fri, 09 Nov 2012 15:43:24 +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
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [renum] [Fwd: I-D Action: draft-carpenter-6renum-next-steps-00.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, 09 Nov 2012 15:43:14 -0000

Hi,

Here is an I-D version of the next steps discussion from yesterday.
There is no intention for this to become an RFC.

Comments are welcome of course, but this is intended only as a brief
list of work to be done elsewhere, not in 6man.

   Brian + Sheng

-------- Original Message --------
Subject: I-D Action: draft-carpenter-6renum-next-steps-00.txt
Date: Fri, 09 Nov 2012 07:31:06 -0800
From: internet-drafts@ietf.org
Reply-To: internet-drafts@ietf.org
To: i-d-announce@ietf.org


A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title           : Next Steps for Renumbering IPv6 Sites
	Author(s)       : Brian Carpenter
                          Sheng Jiang
	Filename        : draft-carpenter-6renum-next-steps-00.txt
	Pages           : 6
	Date            : 2012-11-09

Abstract:
   This document summarises for the record the next steps proposed
   following the completion of chartered work in the 6RENUM WG.  It is
   not expected to become an RFC.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-carpenter-6renum-next-steps-00


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 leo.liubing@huawei.com  Mon Nov 19 18:58:04 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 B315D21E804B; Mon, 19 Nov 2012 18:58:04 -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 6THzCccgMXKf; Mon, 19 Nov 2012 18:58:04 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 637EF21F880B; Mon, 19 Nov 2012 18:58:02 -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 ALS36324; Tue, 20 Nov 2012 02:58:01 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 20 Nov 2012 02:57:32 +0000
Received: from SZXEML441-HUB.china.huawei.com (10.82.67.179) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 20 Nov 2012 02:58:00 +0000
Received: from SZXEML509-MBX.china.huawei.com ([10.82.67.37]) by szxeml441-hub.china.huawei.com ([10.82.67.179]) with mapi id 14.01.0323.003; Tue, 20 Nov 2012 10:57:48 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "renum@ietf.org" <renum@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Thread-Topic: Parameterized IP-Specific configuration
Thread-Index: Ac3GytyaCifxN5uFQxWNBrqucXz6Pw==
Date: Tue, 20 Nov 2012 02:57:48 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453CAB2737@szxeml509-mbx>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-hashedpuzzle: Cvoq Ejoh GFJu HncF IbnU L5zq VYJ5 XuKW ZFTw bNIk oX4u qx0D uW+q v5gQ v9/h xGyH; 7; YgByAGkAYQBuAC4AZQAuAGMAYQByAHAAZQBuAHQAZQByAEAAZwBtAGEAaQBsAC4AYwBvAG0AOwBpAHAAdgA2AEAAaQBlAHQAZgAuAG8AcgBnADsAbABlAGUAQABhAHMAZwBhAHIAZAAuAG8AcgBnADsAcgBlAG4AdQBtAEAAaQBlAHQAZgAuAG8AcgBnADsAcwB0AGkAZwBAAGMAaQBzAGMAbwAuAGMAbwBtADsAdABqAGMAQABlAGMAcwAuAHMAbwB0AG8AbgAuAGEAYwAuAHUAawA7AHcAZQBzAGwAZQB5AC4AZwBlAG8AcgBnAGUAQAB0AHcAYwBhAGIAbABlAC4AYwBvAG0A; Sosha1_v1; 7; {C765E0DF-82B5-4DBE-BA0B-41A6F6EB84A9}; bABlAG8ALgBsAGkAdQBiAGkAbgBnAEAAaAB1AGEAdwBlAGkALgBjAG8AbQA=; Tue, 20 Nov 2012 02:58:17 GMT; UABhAHIAYQBtAGUAdABlAHIAaQB6AGUAZAAgAEkAUAAtAFMAcABlAGMAaQBmAGkAYwAgAGMAbwBuAGYAaQBnAHUAcgBhAHQAaQBvAG4A
x-cr-puzzleid: {C765E0DF-82B5-4DBE-BA0B-41A6F6EB84A9}
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
Cc: Stig Venaas <stig@cisco.com>
Subject: [renum] Parameterized IP-Specific configuration
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, 20 Nov 2012 02:58:04 -0000

Hi, all

This is not talking about a new idea. The " Parameterized IP-Specific confi=
guration" comes from the 6renum WG item, see http://tools.ietf.org/html/dra=
ft-ietf-6renum-gap-analysis-04#page-11

The draft is under 6renum WGLC, according to the comment in the Atlanta mee=
ting, we need your review/comment of whether the "Parameterized IP-specific=
 configuration" is a proper expression.
And if you still have other comments of the document, that would be also ap=
preciated very much.

Thanks a lot.

B.R.
Bing


****For your convenient, abstract the original texts here****
(In draft-ietf-6renum-gap-analysis-04#page-11)

6.3. Parameterized IP-specific Configuration

   Besides the DNS records and the in-host server address entries, there
   are also many places in which the IP addresses are configured, for
   example, filters such as ACL and routing policies, etc. There are
   even more sophisticated cases where the IP addresses are used for
   deriving values, for example, using the unique portion of the
   loopback address to generate an ISIS net ID.

   Ideally, a layer of abstraction for IP-specific configuration within
   various devices (routers, switches, hosts, servers, etc.) is needed.
   However, this cannot be achieved in one step. One possible
   improvement is to make the IP-specific configuration parameterized.
   Two aspects of parameterized configuration could be considered to
   achieve this.
...

Here's an example (not in the draft, just for your easy understanding the a=
bove texts.)
First, we define the addresses for a given interface interface gigabitether=
net1/1
ipv4 address 192.0.2.10/24
ipv6 address 2001:db8::10/64

Note that these addresses could also be automatically configured using DHCP=
 or SLAAC, perhaps then the example would be:
Interface gigabitethernet1/1
ipv4 address dynamic dhcp
ipv6 address dynamic dhcpv6

then elsewhere in the configuration:

access-list example1
permit ipv4 any [gigabitethernet1/1] mask /24 #this permits any ip address =
that matches the prefix assigned to the interface in brackets [], in the ra=
nge defined by the subnet mask at the end of the command permit ipv6 any [g=
igabitethernet1/1] mask /48 #this is the ipv6 equivalent, but permits any a=
ddress in the entire /48

Similar examples could be possible for a BGP session, snmp source address, =
etc. Anywhere else you would hard-code an IP address could use a parameter =
to invoke an address inherited from an interface.

From tjc@ecs.soton.ac.uk  Tue Nov 20 10:30:09 2012
Return-Path: <tjc@ecs.soton.ac.uk>
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 CB0A721F85C3; Tue, 20 Nov 2012 10:30:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.403
X-Spam-Level: 
X-Spam-Status: No, score=-2.403 tagged_above=-999 required=5 tests=[AWL=0.196,  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 P2uajI1kakIi; Tue, 20 Nov 2012 10:30:09 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id E25AE21F8475; Tue, 20 Nov 2012 10:30:08 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id qAKIU1f1009229;  Tue, 20 Nov 2012 18:30:01 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk qAKIU1f1009229
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1353436202; bh=IVb7osJQSTZ4ZnZ6tdREMt6mhhg=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=jsNBHwRQP7Qch2Nxeu6n9y+PZ2oXJwEDNUSc19gs9nKjq27epJSyB6/s21afDmMge b39C42740JPGeKFmvx3ONEr/eALUi0HXYTayL47tef18vbLpNwg+2JcbYsPvFbbXoV W8s7tDiw4yER/qQdwE153BfaO9xPrDh7poOVHwwg=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id oAJIU10430658737g2 ret-id none; Tue, 20 Nov 2012 18:30:01 +0000
Received: from [192.168.1.102] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id qAKITsf5018340 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 20 Nov 2012 18:29:55 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <50ABBCB3.3010402@cisco.com>
Date: Tue, 20 Nov 2012 18:29:53 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|56a0bf66ac9a6146eb8b5da02b42ff35oAJIU103tjc|ecs.soton.ac.uk|2B2CB836-BEC7-4E84-BABB-C7A373E7D25F@ecs.soton.ac.uk>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453CAB2737@szxeml509-mbx> <50ABBCB3.3010402@cisco.com> <2B2CB836-BEC7-4E84-BABB-C7A373E7D25F@ecs.soton.ac.uk>
To: Stig Venaas <stig@cisco.com>
X-Mailer: Apple Mail (2.1499)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=oAJIU1043065873700; tid=oAJIU10430658737g2; client=relay,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: qAKIU1f1009229
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Parameterized IP-Specific configuration
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, 20 Nov 2012 18:30:09 -0000

On 20 Nov 2012, at 17:24, Stig Venaas <stig@cisco.com> wrote:

> On 11/19/2012 6:57 PM, Liubing (Leo) wrote:
>> Hi, all
>>=20
>> This is not talking about a new idea. The " Parameterized IP-Specific =
configuration" comes from the 6renum WG item, see =
http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-04#page-11
>>=20
>> The draft is under 6renum WGLC, according to the comment in the =
Atlanta meeting, we need your review/comment of whether the =
"Parameterized IP-specific configuration" is a proper expression.
>> And if you still have other comments of the document, that would be =
also appreciated very much.
>=20
> Looks good to me. Whether "parametrized" is the correct expression I'm
> not sure. I cannot really find a good/better term for this. The main
> thing is that there is enough detail for people to understand what it =
is
> about. Would it be useful to have an example in the draft (maybe in an
> appendix?). Just so it is clear? I think the current text is fairly
> clear though.

I agree - further comments welcome though.

Tim

> Stig
>=20
>> Thanks a lot.
>>=20
>> B.R.
>> Bing
>>=20
>>=20
>> ****For your convenient, abstract the original texts here****
>> (In draft-ietf-6renum-gap-analysis-04#page-11)
>>=20
>> 6.3. Parameterized IP-specific Configuration
>>=20
>>    Besides the DNS records and the in-host server address entries, =
there
>>    are also many places in which the IP addresses are configured, for
>>    example, filters such as ACL and routing policies, etc. There are
>>    even more sophisticated cases where the IP addresses are used for
>>    deriving values, for example, using the unique portion of the
>>    loopback address to generate an ISIS net ID.
>>=20
>>    Ideally, a layer of abstraction for IP-specific configuration =
within
>>    various devices (routers, switches, hosts, servers, etc.) is =
needed.
>>    However, this cannot be achieved in one step. One possible
>>    improvement is to make the IP-specific configuration =
parameterized.
>>    Two aspects of parameterized configuration could be considered to
>>    achieve this.
>> ...
>>=20
>> Here's an example (not in the draft, just for your easy understanding =
the above texts.)
>> First, we define the addresses for a given interface interface =
gigabitethernet1/1
>> ipv4 address 192.0.2.10/24
>> ipv6 address 2001:db8::10/64
>>=20
>> Note that these addresses could also be automatically configured =
using DHCP or SLAAC, perhaps then the example would be:
>> Interface gigabitethernet1/1
>> ipv4 address dynamic dhcp
>> ipv6 address dynamic dhcpv6
>>=20
>> then elsewhere in the configuration:
>>=20
>> access-list example1
>> permit ipv4 any [gigabitethernet1/1] mask /24 #this permits any ip =
address that matches the prefix assigned to the interface in brackets =
[], in the range defined by the subnet mask at the end of the command =
permit ipv6 any [gigabitethernet1/1] mask /48 #this is the ipv6 =
equivalent, but permits any address in the entire /48
>>=20
>> Similar examples could be possible for a BGP session, snmp source =
address, etc. Anywhere else you would hard-code an IP address could use =
a parameter to invoke an address inherited from an interface.
>>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From stig@cisco.com  Tue Nov 20 09:24:05 2012
Return-Path: <stig@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 D05C421F87D2; Tue, 20 Nov 2012 09:24:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 GAQWSAzS-FqJ; Tue, 20 Nov 2012 09:24:03 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id DB8C621F87BA; Tue, 20 Nov 2012 09:24:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3023; q=dns/txt; s=iport; t=1353432244; x=1354641844; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=5zVJNorkxSlQLmdU0LnmSN6nlah5nr49/D+JMP3TumY=; b=k0n7Mpg03C5cWz+K9SgFdyVWeMj+Gr2mUUfZB8DXbrvBEo0AafXi0aN7 J7cthiHdtJOdz7oT6rnigP+nzykLinkYGBrlC2s7VchaubQUvb8o6PkBi 5JJqkQTxA0Kw6UItdG7z7QDexQ/RqcGRDIZQ8k8BDzfuYU9Jxb6dXs0Dn 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAMK7q1CrRDoI/2dsb2JhbABFwloWc4IeAQEBAwE4QAEFCwsYCRYPCQMCAQIBRQYNAQcBAYgDBQywGJBPjDWEdQOIXI0igRyET4pWgxA
X-IronPort-AV: E=McAfee;i="5400,1158,6902"; a="64424922"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 20 Nov 2012 17:24:03 +0000
Received: from [10.33.12.93] ([10.33.12.93]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id qAKHO3wM027683; Tue, 20 Nov 2012 17:24:03 GMT
Message-ID: <50ABBCB3.3010402@cisco.com>
Date: Tue, 20 Nov 2012 09:24:03 -0800
From: Stig Venaas <stig@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Liubing (Leo)" <leo.liubing@huawei.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453CAB2737@szxeml509-mbx>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453CAB2737@szxeml509-mbx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 21 Nov 2012 00:42:24 -0800
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Parameterized IP-Specific configuration
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, 20 Nov 2012 17:24:06 -0000

On 11/19/2012 6:57 PM, Liubing (Leo) wrote:
> Hi, all
>
> This is not talking about a new idea. The " Parameterized IP-Specific configuration" comes from the 6renum WG item, see http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-04#page-11
>
> The draft is under 6renum WGLC, according to the comment in the Atlanta meeting, we need your review/comment of whether the "Parameterized IP-specific configuration" is a proper expression.
> And if you still have other comments of the document, that would be also appreciated very much.

Looks good to me. Whether "parametrized" is the correct expression I'm
not sure. I cannot really find a good/better term for this. The main
thing is that there is enough detail for people to understand what it is
about. Would it be useful to have an example in the draft (maybe in an
appendix?). Just so it is clear? I think the current text is fairly
clear though.

Stig

> Thanks a lot.
>
> B.R.
> Bing
>
>
> ****For your convenient, abstract the original texts here****
> (In draft-ietf-6renum-gap-analysis-04#page-11)
>
> 6.3. Parameterized IP-specific Configuration
>
>     Besides the DNS records and the in-host server address entries, there
>     are also many places in which the IP addresses are configured, for
>     example, filters such as ACL and routing policies, etc. There are
>     even more sophisticated cases where the IP addresses are used for
>     deriving values, for example, using the unique portion of the
>     loopback address to generate an ISIS net ID.
>
>     Ideally, a layer of abstraction for IP-specific configuration within
>     various devices (routers, switches, hosts, servers, etc.) is needed.
>     However, this cannot be achieved in one step. One possible
>     improvement is to make the IP-specific configuration parameterized.
>     Two aspects of parameterized configuration could be considered to
>     achieve this.
> ...
>
> Here's an example (not in the draft, just for your easy understanding the above texts.)
> First, we define the addresses for a given interface interface gigabitethernet1/1
> ipv4 address 192.0.2.10/24
> ipv6 address 2001:db8::10/64
>
> Note that these addresses could also be automatically configured using DHCP or SLAAC, perhaps then the example would be:
> Interface gigabitethernet1/1
> ipv4 address dynamic dhcp
> ipv6 address dynamic dhcpv6
>
> then elsewhere in the configuration:
>
> access-list example1
> permit ipv4 any [gigabitethernet1/1] mask /24 #this permits any ip address that matches the prefix assigned to the interface in brackets [], in the range defined by the subnet mask at the end of the command permit ipv6 any [gigabitethernet1/1] mask /48 #this is the ipv6 equivalent, but permits any address in the entire /48
>
> Similar examples could be possible for a BGP session, snmp source address, etc. Anywhere else you would hard-code an IP address could use a parameter to invoke an address inherited from an interface.
>


From teco@inf-net.nl  Wed Nov 21 04:35:17 2012
Return-Path: <teco@inf-net.nl>
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 655C321F84C0 for <renum@ietfa.amsl.com>; Wed, 21 Nov 2012 04:35:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 fNwgyaS1IJ60 for <renum@ietfa.amsl.com>; Wed, 21 Nov 2012 04:35:16 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 9972421F84CA for <renum@ietf.org>; Wed, 21 Nov 2012 04:35:16 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id hm6so1545793wib.13 for <renum@ietf.org>; Wed, 21 Nov 2012 04:35:15 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=QUYOQnT6LqwxtDI5Qg+snmHkeTyE+tgVJ4G/HMprhko=; b=DCVtA7cm09Drr4oSWqRBgLEf3i3BUTSglcwZdVcLoG9PgDvfIzQc/OsYCBI+7lWLHk b3bHAj3qVIilwJE3NLjR4GLLDeN2NZdbc0et+QDdIYmw5rsS37yz7pw6KpTyDRg5Fwks mHLFz3GBvM6FlvXrC9RJWQ1E+iZU7+M5kh/N+V6bvKFw//OZGY2xDNtGcSYrFNRmKlPO gyUb356G5KV5uVVlUyPjTbGmWOFDQxZzm5C+uXEDm6xEw6zOIvE734/sAWtMYwgpeniW OdOPmw5hSSzs+Jhs7MxGOM4xJjOALUCHPGDn2OWCXpTVMSVXZ9sbk3L6TeJPoAFWqZIZ AbjQ==
Received: by 10.180.101.231 with SMTP id fj7mr19570121wib.4.1353501315804; Wed, 21 Nov 2012 04:35:15 -0800 (PST)
Received: from [172.16.4.198] ([188.205.88.52]) by mx.google.com with ESMTPS id en20sm24574520wid.4.2012.11.21.04.35.14 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 21 Nov 2012 04:35:15 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <50ABBCB3.3010402@cisco.com>
Date: Wed, 21 Nov 2012 13:35:13 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <62E95934-E7A4-45BD-B4D6-B69FB3BED981@inf-net.nl>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453CAB2737@szxeml509-mbx> <50ABBCB3.3010402@cisco.com>
To: Stig Venaas <stig@cisco.com>
X-Mailer: Apple Mail (2.1283)
X-Gm-Message-State: ALoCoQm25WPPIOk2fjWP0XZ8xluH1zkYj3ZMRIfxZuFNS5ko8zrYmmhet3/NIWsKcu1nPtQbxlQe
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Parameterized IP-Specific configuration
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, 21 Nov 2012 12:35:17 -0000

Op 20 nov. 2012, om 18:24 heeft Stig Venaas het volgende geschreven:

>> IP-Specific configuration

What about "IP configuration for dynamic IP addresses"?

Teco

From wesley.george@twcable.com  Wed Nov 21 07:28:22 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 68D9121F855F; Wed, 21 Nov 2012 07:28:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.403
X-Spam-Level: 
X-Spam-Status: No, score=-0.403 tagged_above=-999 required=5 tests=[AWL=0.060,  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 JrpM5NoYkGrc; Wed, 21 Nov 2012 07:28:22 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id A563721F844F; Wed, 21 Nov 2012 07:28:21 -0800 (PST)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.83,293,1352091600"; d="scan'208";a="455848798"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 21 Nov 2012 10:28:04 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Wed, 21 Nov 2012 10:28:20 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Teco Boot <teco@inf-net.nl>, Stig Venaas <stig@cisco.com>
Date: Wed, 21 Nov 2012 10:28:25 -0500
Thread-Topic: [renum] Parameterized IP-Specific configuration
Thread-Index: Ac3H5KuEHsgUJiYlQBulM7w5IYUTQAAFuMLA
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD592303385FBC7F@PRVPEXVS15.corp.twcable.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453CAB2737@szxeml509-mbx> <50ABBCB3.3010402@cisco.com> <62E95934-E7A4-45BD-B4D6-B69FB3BED981@inf-net.nl>
In-Reply-To: <62E95934-E7A4-45BD-B4D6-B69FB3BED981@inf-net.nl>
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
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Parameterized IP-Specific configuration
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, 21 Nov 2012 15:28:22 -0000

> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf
> Of Teco Boot
>
>
> Op 20 nov. 2012, om 18:24 heeft Stig Venaas het volgende geschreven:
>
> >> IP-Specific configuration
>
> What about "IP configuration for dynamic IP addresses"?
>

[WEG] I'm not keen on that nomenclature because it's not really limited to =
dynamic IP addresses. The idea is more one of inheritance, where configurat=
ion elsewhere uses addresses referenced based on the interface rather than =
explicitly defined. In other words, use a variable in things like ACLs, ins=
tead of the explicit value, and the variable's value is defined based on th=
e interface it references. The addresses themselves can be assigned either =
via dynamic or static methods, and the idea being discussed here is really =
agnostic as to which method is used.

Thanks
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 tom.taylor.stds@gmail.com  Wed Nov 21 07:54:58 2012
Return-Path: <tom.taylor.stds@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 B727521F872E; Wed, 21 Nov 2012 07:54:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.455
X-Spam-Level: 
X-Spam-Status: No, score=-3.455 tagged_above=-999 required=5 tests=[AWL=0.144,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 e6ZeaG-oCMZu; Wed, 21 Nov 2012 07:54:58 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2F1DC21F86BF; Wed, 21 Nov 2012 07:54:58 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so3290466ieb.31 for <multiple recipients>; Wed, 21 Nov 2012 07:54:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-antivirus:x-antivirus-status; bh=FEPQbA81YPW+adjMNV+cS9BlZeUcwtoutv9xXPXwsgQ=; b=I8et0uakCUYj6S/I7KG1LRFSEyDNPRq46gZu+dfJxx0q8+iVEVYcfwD6NM0rlc49+l 7kspzPnUoD5cng0x/g2khjeeOrpVQvNmJDJtuLasnyPlypdeDXtCktsSHa3dnpUT1xTZ vEmfnrjzTFJZjIf2FUpwDTYqZTxlTP/uhUjanhq++2BkGLoAekgwbrLiNmEHCpYUi70E OM5D5f7tKhxtpH5Q4lkENNTL56ifHhqXW/yUBFNqCDpevOMaBqIrCykMJJDqup0agJj1 wB/t0MRStk+5+vkYVCLuSBPZR3QZkgPPiro0siTpOfCKdqI6SlMIu3Xc05ypQn3q9ZZ+ +RwQ==
Received: by 10.50.169.100 with SMTP id ad4mr14116382igc.50.1353513297552; Wed, 21 Nov 2012 07:54:57 -0800 (PST)
Received: from [127.0.0.1] (dsl-173-206-12-215.tor.primus.ca. [173.206.12.215]) by mx.google.com with ESMTPS id xn10sm12138320igb.4.2012.11.21.07.54.55 (version=SSLv3 cipher=OTHER); Wed, 21 Nov 2012 07:54:56 -0800 (PST)
Message-ID: <50ACF94E.4030309@gmail.com>
Date: Wed, 21 Nov 2012 10:54:54 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "George, Wes" <wesley.george@twcable.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453CAB2737@szxeml509-mbx> <50ABBCB3.3010402@cisco.com> <62E95934-E7A4-45BD-B4D6-B69FB3BED981@inf-net.nl> <2671C6CDFBB59E47B64C10B3E0BD592303385FBC7F@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD592303385FBC7F@PRVPEXVS15.corp.twcable.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 121121-0, 21/11/2012), Outbound message
X-Antivirus-Status: Clean
X-Mailman-Approved-At: Wed, 21 Nov 2012 07:55:56 -0800
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "renum@ietf.org" <renum@ietf.org>, Stig Venaas <stig@cisco.com>
Subject: Re: [renum] Parameterized IP-Specific configuration
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, 21 Nov 2012 15:54:58 -0000

Sounds like we're talking about templates.

On 21/11/2012 10:28 AM, George, Wes wrote:
>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On
>> Behalf Of Teco Boot
>>
>>
>> Op 20 nov. 2012, om 18:24 heeft Stig Venaas het volgende
>> geschreven:
>>
>>>> IP-Specific configuration
>>
>> What about "IP configuration for dynamic IP addresses"?
>>
>
> [WEG] I'm not keen on that nomenclature because it's not really
> limited to dynamic IP addresses. The idea is more one of inheritance,
> where configuration elsewhere uses addresses referenced based on the
> interface rather than explicitly defined. In other words, use a
> variable in things like ACLs, instead of the explicit value, and the
> variable's value is defined based on the interface it references. The
> addresses themselves can be assigned either via dynamic or static
> methods, and the idea being discussed here is really agnostic as to
> which method is used.
>
> Thanks Wes George
>
...

From teco@inf-net.nl  Wed Nov 21 08:01:32 2012
Return-Path: <teco@inf-net.nl>
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 E453021F8826 for <renum@ietfa.amsl.com>; Wed, 21 Nov 2012 08:01:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.423
X-Spam-Level: 
X-Spam-Status: No, score=-3.423 tagged_above=-999 required=5 tests=[AWL=0.176,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Na3VW9AhCZap for <renum@ietfa.amsl.com>; Wed, 21 Nov 2012 08:01:31 -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 20CE121F892A for <renum@ietf.org>; Wed, 21 Nov 2012 08:01:30 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id a1so2333742eaa.31 for <renum@ietf.org>; Wed, 21 Nov 2012 08:01:29 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=RjmHgtZ1vm/Qc2qGXKE2JoYy4Pbm/ckLhThQCQV7mPA=; b=i86sm4uiEoAXGc2OU2BHPYT+K89YX85tyLVSrHn0qzRdY2miapL88N70M0lS6GC61l FyBujlEPx5yMUSCHeiDuEB7XhvBMmXXGzsZiqhUvBqLnLsxwD5rnZle5cYsprKlHWFLD Az8R1tExls39Iov0h6rey+cOyCZ57VFE6BcfqK9V9GdJD1RI8uaUB0iIOy4qncH/erB3 xdvq1abmZaFzTFPQBPpwKi0Ka0g30EeTasRN6VKtgt1x4wI3wUqwFd6O9rX+UUd1w9A/ DYFSxTwy090q+pvT6qqWL48Z3hwcVX2q+tfTWzDHdStyi3xbYLGa4rsfYM4SWBINAWYL ki3A==
Received: by 10.14.211.135 with SMTP id w7mr39057181eeo.4.1353513689805; Wed, 21 Nov 2012 08:01:29 -0800 (PST)
Received: from [10.87.66.130] ([80.187.201.33]) by mx.google.com with ESMTPS id e2sm954990eeo.8.2012.11.21.08.01.14 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 21 Nov 2012 08:01:29 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD592303385FBC7F@PRVPEXVS15.corp.twcable.com>
Date: Wed, 21 Nov 2012 16:58:30 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D9C1A573-2C99-4A9C-A795-CFC831575040@inf-net.nl>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453CAB2737@szxeml509-mbx> <50ABBCB3.3010402@cisco.com> <62E95934-E7A4-45BD-B4D6-B69FB3BED981@inf-net.nl> <2671C6CDFBB59E47B64C10B3E0BD592303385FBC7F@PRVPEXVS15.corp.twcable.com>
To: "George, Wes" <wesley.george@twcable.com>
X-Mailer: Apple Mail (2.1283)
X-Gm-Message-State: ALoCoQlMBvBBzVen3Y5ZavJ4OJ3GlDreTxtfAf63qB3UHH9ffTslJGoW5R6ZWBZlqqCCYm5oIlbj
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "renum@ietf.org" <renum@ietf.org>, Stig Venaas <stig@cisco.com>
Subject: Re: [renum] Parameterized IP-Specific configuration
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, 21 Nov 2012 16:01:33 -0000

Op 21 nov. 2012, om 16:28 heeft George, Wes het volgende geschreven:

>> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On =
Behalf
>> Of Teco Boot
>>=20
>>=20
>> Op 20 nov. 2012, om 18:24 heeft Stig Venaas het volgende geschreven:
>>=20
>>>> IP-Specific configuration
>>=20
>> What about "IP configuration for dynamic IP addresses"?
>>=20
>=20
> [WEG] I'm not keen on that nomenclature because it's not really =
limited to dynamic IP addresses. The idea is more one of inheritance, =
where configuration elsewhere uses addresses referenced based on the =
interface rather than explicitly defined. In other words, use a variable =
in things like ACLs, instead of the explicit value, and the variable's =
value is defined based on the interface it references. The addresses =
themselves can be assigned either via dynamic or static methods, and the =
idea being discussed here is really agnostic as to which method is used.
OK. But with static IP addresses, the config procedure / tool can parse =
and actual config can make use of literals. With dynamic IP addresses, =
this is no option.

I agree on that the variable, used for configuring addresses, could be =
configured statically somewhere in the config. Can make IP diagrams more =
readable also, I use p1:: p2:: etc. a lot. With a legend somewhere.

Teco

>=20
> Thanks
> Wes George
>=20
> This E-mail and any of its attachments may contain Time Warner Cable =
proprietary information, which is privileged, confidential, or subject =
to copyright belonging to Time Warner Cable. This E-mail is intended =
solely for the use 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 dissemination, distribution, copying, or action taken =
in relation to the contents of and attachments to this E-mail is =
strictly prohibited and may be unlawful. If you have received this =
E-mail in error, please notify the sender immediately and permanently =
delete the original and any copy of this E-mail and any printout.


From internet-drafts@ietf.org  Tue Nov 27 20:59:34 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 80AF821F8624; Tue, 27 Nov 2012 20:59:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.545
X-Spam-Level: 
X-Spam-Status: No, score=-102.545 tagged_above=-999 required=5 tests=[AWL=0.054, 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 wkmED0yNfUDG; Tue, 27 Nov 2012 20:59:34 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E2F321F858B; Tue, 27 Nov 2012 20:59:34 -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: <20121128045934.31215.4986.idtracker@ietfa.amsl.com>
Date: Tue, 27 Nov 2012 20:59:34 -0800
Cc: renum@ietf.org
Subject: [renum] I-D Action: draft-ietf-6renum-enterprise-04.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, 28 Nov 2012 04:59:34 -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 and Guidel=
ines
	Author(s)       : Sheng Jiang
                          Bing Liu
                          Brian Carpenter
	Filename        : draft-ietf-6renum-enterprise-04.txt
	Pages           : 17
	Date            : 2012-11-27

Abstract:
   This document analyzes events that cause renumbering and describes
   the best renumbering practice. Best practices 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-04

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


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


From leo.liubing@huawei.com  Tue Nov 27 21:09:56 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 7CA3A21E8030 for <renum@ietfa.amsl.com>; Tue, 27 Nov 2012 21:09:56 -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 R+MnF9Mq0wKC for <renum@ietfa.amsl.com>; Tue, 27 Nov 2012 21:09:55 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C8E8E21F87A0 for <renum@ietf.org>; Tue, 27 Nov 2012 21:09:53 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ANG02428; Wed, 28 Nov 2012 05:09:50 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 28 Nov 2012 05:09:23 +0000
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 28 Nov 2012 05:09:31 +0000
Received: from SZXEML509-MBS.china.huawei.com ([10.82.67.53]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0323.003; Wed, 28 Nov 2012 13:09:21 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "renum@ietf.org" <renum@ietf.org>
Thread-Topic: [renum] I-D Action: draft-ietf-6renum-enterprise-04.txt
Thread-Index: AQHNzSUslz0j9kc+4U+zTPaqQ4/1bZf+shmQ
Date: Wed, 28 Nov 2012 05:09:21 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453CCE561C@szxeml509-mbs>
References: <20121128045934.31215.4986.idtracker@ietfa.amsl.com>
In-Reply-To: <20121128045934.31215.4986.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
Cc: Stig Venaas <stig@cisco.com>
Subject: Re: [renum] I-D Action: draft-ietf-6renum-enterprise-04.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, 28 Nov 2012 05:09:56 -0000

Hi, all

A new version of enterprise renumbering scenario draft has been posted.
Most are editorial revisions according to AD's (Ron) review.

Thanks.
Bing

> -----Original Message-----
> From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: Wednesday, November 28, 2012 1:00 PM
> To: i-d-announce@ietf.org
> Cc: renum@ietf.org
> Subject: [renum] I-D Action: draft-ietf-6renum-enterprise-04.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>  This draft is a work item of the IPv6 Site Renumbering Working Group of =
the
> IETF.
>=20
> 	Title           : IPv6 Enterprise Network Renumbering Scenarios and
> Guidelines
> 	Author(s)       : Sheng Jiang
>                           Bing Liu
>                           Brian Carpenter
> 	Filename        : draft-ietf-6renum-enterprise-04.txt
> 	Pages           : 17
> 	Date            : 2012-11-27
>=20
> Abstract:
>    This document analyzes events that cause renumbering and describes
>    the best renumbering practice. Best practices are described in three
>    categories: those applicable during network design, those applicable
>    during preparation for renumbering, and those applicable during the
>    renumbering operation.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6renum-enterprise
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6renum-enterprise-04
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-enterprise-04
>=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 iesg-secretary@ietf.org  Wed Nov 28 07:19:33 2012
Return-Path: <iesg-secretary@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 150DB21F8905; Wed, 28 Nov 2012 07:19:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.496
X-Spam-Level: 
X-Spam-Status: No, score=-102.496 tagged_above=-999 required=5 tests=[AWL=0.103, 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 bFf5jQJ+TzXR; Wed, 28 Nov 2012 07:19:32 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A34E21F88E9; Wed, 28 Nov 2012 07:19:32 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.36
Message-ID: <20121128151932.12926.94147.idtracker@ietfa.amsl.com>
Date: Wed, 28 Nov 2012 07:19:32 -0800
Cc: renum@ietf.org
Subject: [renum] Last Call: <draft-ietf-6renum-enterprise-04.txt> (IPv6 Enterprise	Network Renumbering Scenarios and Guidelines) to Informational RFC
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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, 28 Nov 2012 15:19:33 -0000

The IESG has received a request from the IPv6 Site Renumbering WG
(6renum) to consider the following document:
- 'IPv6 Enterprise Network Renumbering Scenarios and Guidelines'
  <draft-ietf-6renum-enterprise-04.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-12-12. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document analyzes events that cause renumbering and describes
   the best renumbering practice. Best practices are described in three
   categories: those applicable during network design, those applicable
   during preparation for renumbering, and those applicable during the
   renumbering operation.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-6renum-enterprise/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-6renum-enterprise/ballot/


No IPR declarations have been submitted directly on this I-D.



From iesg-secretary@ietf.org  Wed Nov 28 07:25:44 2012
Return-Path: <iesg-secretary@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 14E5221F87F3; Wed, 28 Nov 2012 07:25:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.503
X-Spam-Level: 
X-Spam-Status: No, score=-102.503 tagged_above=-999 required=5 tests=[AWL=0.096, 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 vvip2KUQ+OFB; Wed, 28 Nov 2012 07:25:43 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8611221F858C; Wed, 28 Nov 2012 07:25:43 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.36
Message-ID: <20121128152543.31789.28197.idtracker@ietfa.amsl.com>
Date: Wed, 28 Nov 2012 07:25:43 -0800
Cc: renum@ietf.org
Subject: [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
Reply-To: ietf@ietf.org
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, 28 Nov 2012 15:25:44 -0000

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

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-12-12. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


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




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-6renum-static-problem/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-6renum-static-problem/ballot/


No IPR declarations have been submitted directly on this I-D.


