[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: I-D ACTION:draft-baker-v6ops-end2end-00.txt
A few comments (mostly nits).
1. This is the first time I have seen a draft that refers to it's self as a
note ( in the abstract and introduction), this seems like the wrong word.
2. In the last sentence of section 2.1 it reads:
"IPv4, there is at minimum IPv4 connectivity",
I recommend it read:
"IPv4, there is at a minimum IPv4 connectivity"
3. In the last sentence of section 3 it reads:
' "A satisfactory solution", it could be said, "contains no unnecessary
complexity", and "first, does no harm." '
This seems a little confusing, as the one with first is second or last. It
may be confusing for non-native English speakers.
4. In section 3.1, in the third paragraph ("If the central IPv4 networks are
providing the"), is this referring to the backbone or interconnection points
(like the public MAE (east/west) Internet Exchange or any of the hundreds of
private ones)? Are there any drafts that talk about converting the backbones
or interconnection points to IPv6 using any of the methods used (tunnel
broker, etc) or are they all end network based (like Tredeo, etc). If not
then this or another one might help solve some of the problems you are
For example MAE (run by MCI http://www.mae.net/svc/mae-ipv6.htm) states:
IPv6 and IPv6 peering services reside on the same level 2 exchange
switch fabric. IPv6 is
transparent to the switching platform and the access type (ATM, Frame,
or GigE), and the
connections are supported by PeerMaker. Customers may choose to use a
separate port for
IPv6 or share the same port among IPv6 and IPv4 connections. The service
dual-stack, tunneling connections configurations.
IPv6 is not supported for interworked connections between a GigE port
and either a Frame
or ATM port.
Please note that they support tunneling, but do not say which type (just as
----- Original Message -----
Sent: Monday, August 15, 2005 10:50 PM
Subject: I-D ACTION:draft-baker-v6ops-end2end-00.txt
> A New Internet-Draft is available from the on-line Internet-Drafts
> Title : The End to End Problem in a fully generalized
> IPv4, IPv6, and IPv4+IPv6 network
> Author(s) : F. Baker
> Filename : draft-baker-v6ops-end2end-00.txt
> Pages : 23
> Date : 2005-8-15
> This note is intended to describe the end to end problem as it
> applies to a network of networks, wherein some component networks
> independently run only IPv4 with or without a transition mechanism,
> some run only IPv6 with or without a transition mechanism and
> coordination of transition mechanisms, and some run IPv4 and IPv6 in
> parallel supporting native routing.
> A URL for this Internet-Draft is:
> To remove yourself from the I-D Announcement list, send a message to
> email@example.com 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
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> "get draft-baker-v6ops-end2end-00.txt".
> A list of Internet-Drafts directories can be found in
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> Internet-Drafts can also be obtained by e-mail.
> Send a message to:
> In the body type:
> "FILE /internet-drafts/draft-baker-v6ops-end2end-00.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
> 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
> CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY
> In order to maintain computing infrastructure integrity, Cisco Systems
> Enterprise Messaging Services and InfoSec teams have set a mail policy
> disallowing executable attachments in email.
> This message contained an executable attachment type that is prohibited
> by this policy. The attachment has been removed from this message and
> copied to quarantine by our systems. It will be held in quarantine for
> seven days in the event that the content needs to be retrieved.
> Please be aware many viruses attempt to look like legitimate email or
> notifications from anti-virus systems. We will clearly mark a seperation
> between our notifications and the original email as follows:
> "CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY"
> For further reference information about viruses and email antivirus
> efforts within Cisco, please visit:
> If your concern isn't addressed by the information in this notification
> or the above web page, you may open a support request:
> Select "Messaging", "Email-Related", "Mail Routing"
> Please include in the text of your case the following information:
> * Full headers of the message. Documentation on displaying the full
> headers is available at this URL:
> * This unique quarantine identifier: j7FK4TVS011545
> If the matter is urgent, you may follow up by calling one of the below
> referenced numbers. Please make every effort to provide the above
> requested information via the support web tool prior to calling as it
> will greatly aid the resolution of your issue.
> 1 408 526 8888
> +61 2 8446 8888
> +31 20 485 4888
> +81 3 5549 6888
> US (Toll Free)
> 1| 800| 888| 8187| (ext.68888)
> Thank you for your cooperation,
> Enterprise Messaging Services
> Cisco Systems, Inc
> I-D-Announce mailing list