Re: [ipv6-dir] Re: Updated document
Thomas Narten <narten@us.ibm.com> Fri, 06 January 2006 14:54 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eusyg-0005du-SZ; Fri, 06 Jan 2006 09:54:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Eusye-0005cK-UZ; Fri, 06 Jan 2006 09:54:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06376; Fri, 6 Jan 2006 09:52:42 -0500 (EST)
Received: from e34.co.us.ibm.com ([32.97.110.152]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eut4X-000475-8J; Fri, 06 Jan 2006 10:00:05 -0500
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e34.co.us.ibm.com (8.12.11/8.12.11) with ESMTP id k06ErgY0029204; Fri, 6 Jan 2006 09:53:42 -0500
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id k06EqM0o260864; Fri, 6 Jan 2006 07:52:22 -0700
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id k06ErfkD001411; Fri, 6 Jan 2006 07:53:42 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-48-43-36.mts.ibm.com [9.48.43.36]) by d03av03.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id k06Erb0f000868; Fri, 6 Jan 2006 07:53:38 -0700
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.13.1/8.12.5) with ESMTP id k06ErMVv019812; Fri, 6 Jan 2006 09:53:27 -0500
Message-Id: <200601061453.k06ErMVv019812@cichlid.raleigh.ibm.com>
To: john.loughney@nokia.com
Subject: Re: [ipv6-dir] Re: Updated document
In-Reply-To: Message from <john.loughney@nokia.com> of "Fri, 06 Jan 2006 16:39:56 +0200." <1AA39B75171A7144A73216AED1D7478D01869A71@esebe100.NOE.Nokia.com>
Date: Fri, 06 Jan 2006 09:53:22 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 2.2 (++)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: leslie@thinkingcat.com, iab@ietf.org, ipv6-dir@ietf.org, MRW@devicescape.com, loa@pi.se, sob@harvard.edu, sbrim@cisco.com, kurtis@kurtis.pp.se
X-BeenThere: ipv6-dir@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF IPv6 Directorate <ipv6-dir.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6-dir>, <mailto:ipv6-dir-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6-dir@ietf.org>
List-Help: <mailto:ipv6-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6-dir>, <mailto:ipv6-dir-request@ietf.org?subject=subscribe>
Sender: ipv6-dir-bounces@ietf.org
Errors-To: ipv6-dir-bounces@ietf.org
Hi John. > I took this as input: > > Furthermore, it would be very > > helpful and useful for our further collaboration if the IETF could > > inform us of their standards plan regarding IPv6. We will also inform > > the IETF of our ideas in the near future and then commence creating > > Internet drafts to define our requirements. > What I think should be covered, to some extent, are the areas of work > the IETF is doing and invite them to participate in the relevant working > groups in order that their requirements are met. At least that is how > I read the questions wrt QoS signaling. This makes sense to me. And FWIW, I think most of the proposed QOS text is OK. But on the flow label, I wonder if there is too much text, even if it is intended to be tutorial. Can't we just cite the relevant documents and be done with that? > For mobility & multihoming, it would be good to point out the active > areas in the IETF, not propose one way or another as the prefered > mechanism, but more to list what we are doing, so that they can > evaluate them and determine what fits there needs. I agree. Right now, I think it would be hard to tell from the text what those active areas are and how to position their relative importance/applicability. We should be pointing folk to the WGs (rather than specific documents), and let them do their own followup. Later, once they have more specific questions, we can elaborate. But given the vagueness of what is being asked, we need to be just as careful to not be too specific in our response. Or we risk not mentioning some efforts or overemphasizing another. Thomas _______________________________________________ ipv6-dir mailing list ipv6-dir@ietf.org https://www1.ietf.org/mailman/listinfo/ipv6-dir
- [ipv6-dir] Re: Updated document Pekka Nikander
- [ipv6-dir] Re: Updated document Leslie Daigle
- [ipv6-dir] RE: Updated document john.loughney
- [ipv6-dir] Re: Updated document Scott W Brim
- [ipv6-dir] Re: Updated document Scott Bradner
- Re: [ipv6-dir] Re: Updated document Kurt Erik Lindqvist
- Re: [ipv6-dir] Re: Updated document Scott W Brim
- RE: [ipv6-dir] Re: Updated document Loughney John (Nokia-NRC/Helsinki)
- Re: [ipv6-dir] Re: Updated document Thomas Narten
- RE: [ipv6-dir] Re: Updated document john.loughney
- Re: [ipv6-dir] Re: Updated document Thomas Narten
- Re: [ipv6-dir] Re: Updated document Scott W Brim
- Re: [ipv6-dir] Re: Updated document Kurt Erik Lindqvist
- Re: [ipv6-dir] Re: Updated document Kurt Erik Lindqvist
- IAB last call... Re: [ipv6-dir] Re: Updated docum… Leslie Daigle
- Re: [ipv6-dir] Re: Updated document Kurt Erik Lindqvist
- Re: [ipv6-dir] Re: Updated document Brian E Carpenter
- Re: [ipv6-dir] Re: Updated document Brian E Carpenter
- Re: IAB last call... Re: [ipv6-dir] Re: Updated d… Leslie Daigle
- RE: [ipv6-dir] Re: Updated document Margaret Wasserman
- Re: [ipv6-dir] Re: Updated document Scott W Brim
- Re: [ipv6-dir] Re: Updated document Scott W Brim
- Re: [ipv6-dir] Re: Updated document Soininen Jonne (Nokia-NET/Espoo)
- [ipv6-dir] Re: ITU-T liaison re IPv6 Thomas Narten