On Mon, 22 Feb 2010, Brian E Carpenter wrote:
I think it's out of scope of a *protocol* standard. However, I think Doug
has a valid point, so maybe we should add an explicit statement that
the document defines what should be transmitted and presented to humans,
but does not define internal
On 2010-02-25 20:48, Rémi Després wrote:
Brian, Sheng,
The proposal seems nicely stabilized as regards the MSB=0 case.
IMHO though, more than proposed so far could be done concerning the MSB=1
case.
In sec 3, instead of If the MSB of the flow label is 1, the remaining 19
bits MAY obey
On 02/25/10 00:10, Antonio Querubin wrote:
On Mon, 22 Feb 2010, Brian E Carpenter wrote:
I think it's out of scope of a *protocol* standard. However, I think Doug
has a valid point, so maybe we should add an explicit statement that
the document defines what should be transmitted and
Hemant,
I am not sure I understand the "invented
prefix" case above.
IPv4 address assignment API's typically
assigns both an
address and a mask to an interface. One common implementation mistake
by
those familiar with IPv4 is to assume that an address carries a /64
prefix
length
The IESG has received a request from the IPv6 Maintenance WG (6man) to
consider the following document:
- 'IPv6 Subnet Model: the Relationship between Links and Subnet Prefixes '
draft-ietf-6man-ipv6-subnet-model-07.txt as a Proposed Standard
The IESG plans to make a decision in the next few
Sure, Jari, we will update the draft to a 08 in the next 1-3 days and
submit it.
Thanks much!
Hemant
From: Jari Arkko [mailto:jari.ar...@piuha.net]
Sent: Thursday, February 25, 2010 5:24 PM
To: Hemant Singh (shemant)
Cc: IETF IPv6 Mailing List;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian, Doug, Antonio
Thanks for the text idea.
So the final fix will probably look like this.
As IPv6 deployment increases there will be a dramatic increase in the
need to use IPv6 addresses in text.
While the IPv6 address architecture in
On 02/25/10 16:16, Seiichi Kawamura wrote:
Brian, Doug, Antonio
Thanks for the text idea.
So the final fix will probably look like this.
As IPv6 deployment increases there will be a dramatic increase in the
need to use IPv6 addresses in text.
While the IPv6 address architecture
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 Maintenance Working Group of the IETF.
Title : A Recommendation for IPv6 Address Text Representation
Author(s) : S. Kawamura, M. Kawashima
-Original Message-
From: Brian E Carpenter [mailto:brian.e.carpen...@gmail.com]
Sent: Friday, February 26, 2010 4:04 AM
To: Rémi Després
Cc: Sheng Jiang; '6man'
Subject: Re: [Fwd: I-D Action:draft-carpenter-6man-flow-update-00.txt]
On 2010-02-25 20:48, Rémi Després wrote:
-Original Message-
From: Brian E Carpenter [mailto:brian.e.carpen...@gmail.com]
Sent: Friday, February 26, 2010 4:04 AM
To: Rémi Després
Cc: Sheng Jiang; '6man'
Subject: Re: [Fwd: I-D Action:draft-carpenter-6man-flow-update-00.txt]
On 2010-02-25 20:48, Rémi Després wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have committed the changes.
Thanks to everyone that helped.
All issues raised should be clear now.
Regards,
Seiichi
internet-dra...@ietf.org wrote:
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a
12 matches
Mail list logo
