[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I-D ACTION:draft-ietf-v6ops-addcon-03.txt

Hi Gunter,
Some comments to the draft-ietf-v6ops-addcon-03 after request of Fred in the wg meeting. I think the document is well written and gives some useful insights for IPv6 address allocation. 

1.
In introduction the treatment of PI can be simpler - policy might change over the time in different RIRs: 

"In each case the prefix received is provider assigned (PA) or
provider independent (PI).

We do not discuss PI policy here.... "

2.

2.2 para 4 - I am not a native speaker, but I would change:

A site using ULAs may or may not also deploy globals.
|
V
A site using ULAs may or may not also deploy global addresses.


3.
2.2 para 5 - the multicast RPF checks are only applicable in PIM routing enviroment, might be others also. Therefore I would add explicit reference to IPv6 PIM .... 

4.
2.3 6bone address space could be treated more directly. 6bone address space must not be used since this space might be used in the global IPv6 in the future. 


5.

I would consider other hints to configure subnet ids with classification:
- using existing systems
   - translate the existing subnet number into IPv6 subnet id
   - translate the VLAN id into IPv6 subnet id

- rethink
   - allocate according to your need

- aggreagate
   - aggregate according to the topology, service or structure of the
     organisation as described in 2.4
6. The case studies might be moved into an appendix. 

Regards,

Janos Mohacsi
Network Engineer, Research Associate, Head of Network Planning and Projects
NIIF/HUNGARNET, HUNGARY
Key 70EF9882: DEC2 C685 1ED4 C95A 145F  4300 6F64 7B00 70EF 9882

On Mon, 5 Mar 2007, 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 Operations Working Group of the IETF.

	Title		: IPv6 Unicast Address Assignment Considerations
	Author(s)	: G. Van de Velde, et al.
	Filename	: draft-ietf-v6ops-addcon-03.txt
	Pages		: 33
	Date		: 2007-3-5

One fundamental aspect of any IP communications infrastructure is its
  addressing plan.  With its new address architecture and allocation
  policies, the introduction of IPv6 into a network means that network
  designers and operators need to reconsider their existing approaches
  to network addressing.  Lack of guidelines on handling this aspect of
  network design could slow down the deployment and integration of
  IPv6.  This document aims to provide the information and
  recommendations relevant to planning the addressing aspects of IPv6
  deployments.  The document also provides IPv6 addressing case studies
  for both an enterprise and an ISP network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-addcon-03.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
"get draft-ietf-v6ops-addcon-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-v6ops-addcon-03.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.