A draft on this topic has been updated: http://www.ietf.org/internet-drafts/draft-carpenter-renum-needs-work-01.txt Comments and discussion are invited on the OPS Area list, ops-area <at> ietf.org Brian Carpenter Ran Atkinson Hannu Flinck P.S. Apologies if you receive multiple copies, but that seems preferable to cross-posting to multiple lists.
Brian, > A draft on this topic has been updated: > http://www.ietf.org/internet-drafts/draft-carpenter-renum-needs-work-01.txt > > Comments and discussion are invited on the OPS Area list, > ops-area <at> ietf.org I completely agree that renumbering needs more work. For IPv4, I guess that this will always remain difficult. For IPv6, as most networks have still not deployed IPv6 and there are more addresses, there is still some hope. I think that a key point for renumbering is that it should be planned from day one when the first lines of the configuration of a network or network service are written. Every IPv6 operator should expect that he will have to renumber his network one day and should plan for this event. In most cases, there numbering will be due to economic factors such as merging or acquisition. An important recommendation in the draft (section 5.3.4) is that the network configuration should be based on databases and scripts/automated tools. The database stores all the information about the network and the tools derive the configuration from the database. As you note, this way of configuring networks is not the most widespread, but is being used by more network operators. It is also possible to prepare network configurations so that renumbering will be much easier. We have recently proposed a tool based on macros that allows to ease the reconfiguration of a network after a renumbering event. We applied the tool on real DNS, firewall and DHCP(Continue reading)
I believe that this I-D deserves some scrutiny from the OPS folks. Dan -----Original Message----- From: i-d-announce-bounces <at> ietf.org [mailto:i-d-announce-bounces <at> ietf.org] On Behalf Of Internet-Drafts <at> ietf.org Sent: Saturday, January 17, 2009 8:15 PM To: i-d-announce <at> ietf.org Subject: I-D Action:draft-gray-mpls-tp-nm-req-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : MPLS TP Network Management Requirements Author(s) : S. Mansfield, et al. Filename : draft-gray-mpls-tp-nm-req-02.txt Pages : 15 Date : 2009-01-17 This document specifies the requirements necessary to manage the elements and networks that support an MPLS Transport Profile (MPLS-TP). This document is a product of a joint International Telecommunications Union - Telecommunications Standardization Sector (ITU-T) and Internet Engineering Task Force (IETF) effort(Continue reading)
From the list of cut-off dates of IETF-74: > February 2, 2009 Monday - Cutoff date for requests to Area Directors to schedule BOFs at 17:00 PST (01:00 Tuesday, February 3 UTC/GMT). To request a BOF, please see instructions on Requesting a BOF. > February 9, 2009 Monday - Cutoff date for Area Directors to approve BOF requests at 17:00 PST (01:00 Tuesday, February 10 UTC/GMT). In between the IAB and IESG telechat that will review the BOF requests is scheduled for Thursday 2/5. If there are plans to submit any such request in the OPS Area, Ron and me would be interested to hear as soon as possible. Also, we have asked for a 2-hour meeting slot for the OPS Open Area meeting in San Francisco. Please send us any requests for mini-BOFs, presentations or items for discussion at the open area meeting. Thanks and Regards, Ron and Dan
RSS Feed1 | |
|---|---|
2 | |
10 | |
7 | |
2 | |
4 | |
29 | |
4 | |
5 | |
29 | |
10 | |
16 | |
4 | |
2 | |
2 | |
6 | |
13 | |
1 | |
4 | |
3 | |
2 | |
3 | |
7 | |
5 | |
3 | |
1 | |
98 | |
6 | |
20 | |
4 | |
11 | |
17 | |
1 | |
1 | |
12 | |
44 | |
2 | |
19 | |
4 | |
3 | |
25 | |
3 | |
17 | |
8 | |
5 | |
6 | |
13 | |
20 | |
4 | |
8 | |
4 | |
4 | |
16 | |
17 | |
19 | |
16 | |
13 | |
5 | |
17 | |
13 | |
6 | |
21 | |
17 | |
31 | |
13 | |
6 | |
9 | |
36 | |
29 | |
23 | |
71 | |
17 | |
32 | |
15 | |
21 | |
13 | |
2 | |
3 | |
6 | |
1 | |
1 | |
6 | |
1 | |
1 | |
1 | |
15 | |
1 | |
4 | |
2 | |
1 | |
12 | |
1 | |
14 | |
1 | |
2 | |
3 | |
4 | |
3 | |
1 | |
1 | |
3 |
