[ipv6-dir] Re: FW: ITU-T Q.9/13 IPv6 concerns

Scott W Brim <sbrim@cisco.com> Wed, 09 November 2005 03:30 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 1EZgfL-0001BH-3L; Tue, 08 Nov 2005 22:30:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZgB6-0007qU-8a for ipv6-dir@megatron.ietf.org; Tue, 08 Nov 2005 21:59:12 -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 VAA07071 for <ipv6-dir@ietf.org>; Tue, 8 Nov 2005 21:58:44 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZgR2-0005QW-0F for ipv6-dir@ietf.org; Tue, 08 Nov 2005 22:15:40 -0500
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-1.cisco.com with ESMTP; 08 Nov 2005 18:59:03 -0800
X-IronPort-AV: i="3.97,306,1125903600"; d="scan'208"; a="673069210:sNHT25660888"
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id jA92ww4C006551; Tue, 8 Nov 2005 18:59:00 -0800 (PST)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 8 Nov 2005 18:58:58 -0800
Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 8 Nov 2005 18:58:58 -0800
Message-ID: <437165F1.1040301@cisco.com>
Date: Tue, 08 Nov 2005 18:58:57 -0800
From: Scott W Brim <sbrim@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050923 Thunderbird/1.0.7 Mnenhy/0.7.2.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Margaret Wasserman <MRW@devicescape.com>
References: <C86180A8C204554D8A3323D8F6B0A29FB57A7B@dhost002-46.dex002.intermedia.net>
In-Reply-To: <C86180A8C204554D8A3323D8F6B0A29FB57A7B@dhost002-46.dex002.intermedia.net>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Nov 2005 02:58:58.0351 (UTC) FILETIME=[8792D3F0:01C5E4D9]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 08 Nov 2005 22:30:25 -0500
Cc: ipv6-dir@ietf.org
Subject: [ipv6-dir] Re: FW: ITU-T Q.9/13 IPv6 concerns
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

For those who might not have seen them, this came out of
https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=127
and https://datatracker.ietf.org/documents/LIAISON/file182.pdf

Thanks ... Scott

On 11/08/2005 09:59 AM, Margaret Wasserman allegedly wrote:
> Is this something that the IPv6 directorate could prepare a response to?
> Any volunteers to take the lead on getting this together?
> 
> Margaret
> 
> 
> -----Original Message-----
> From: Scott W Brim [mailto:sbrim@cisco.com] 
> Sent: Friday, October 28, 2005 1:17 PM
> To: 'Margaret Wasserman'
> Subject: ITU-T Q.9/13 IPv6 concerns
> 
> Hi Margaret.  Please either (1) tell me which WGs or ADs to direct
> this to, or (2) compile a list of RFCs/drafts yourself.  I'm grateful.
> After we have a list I'll draft up a liaison for you.
> 
> These are some specific things that Q.9/13 is concerned about.  What
> the IETF should do is to send them a list of the relevant drafts and
> RFCs, showing them how these issues are being addressed.
> 
> I would do this myself but I'm not an IPv6 expert and I know I'll miss
> something.  All we need is a list.
> 
> - QoS signaling.  They want to be sure that they can efficiently use
>   both the the transport signaling protocols (such as RSVP and NSIS)
>   and the application signaling protocols (such as SIP) in an IPv6
>   environment.  Relevant RFCs/drafts are those about how those
>   protocols work over IPv6.
> 
> - QoS signaling interworking, IPv4<->IPv6.
> 
> - General IPv4-IPv6.  They are wondering under what conditions
>   application level gateways will be required.
> 
> - Also list the structure of the flow label.  They are very interested
>   in what it can be used for.
> 
> - Multihoming with IPv6.  Nothing surprising here -- just list the
>   latest cool stuff for multihoming (both site and host).  They like
>   SCTP.
> 
> - Mobility.
> 
> - MPLS and IPv6.
> 
> 
> 
> Thanks ... Scott
> 

_______________________________________________
ipv6-dir mailing list
ipv6-dir@ietf.org
https://www1.ietf.org/mailman/listinfo/ipv6-dir