From tsvwg-bounces@ietf.org Wed Aug 01 06:04:25 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGB3x-0003A2-VM; Wed, 01 Aug 2007 06:04:17 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IGB3x-00039l-97
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 06:04:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IGB3w-00037l-Nx
	for tsvwg@ietf.org; Wed, 01 Aug 2007 06:04:16 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGB3v-0000kv-I1
	for tsvwg@ietf.org; Wed, 01 Aug 2007 06:04:16 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 01 Aug 2007 12:04:06 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAMf3r0aQ/uCKh2dsb2JhbACOEAIJCic
X-IronPort-AV: i="4.19,208,1183327200"; 
	d="scan'208"; a="149527348:sNHT3043158268"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l71A45bN007694; 
	Wed, 1 Aug 2007 12:04:05 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l71A43kt007283; 
	Wed, 1 Aug 2007 10:04:05 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Aug 2007 12:04:03 +0200
Received: from [144.254.53.188] ([144.254.53.188]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Aug 2007 12:04:03 +0200
In-Reply-To: <0879C74D-31CA-4F54-BC6D-1B8BC0F44B50@cisco.com>
References: <E1I400A-0005PX-DQ@stiedprstage1.ietf.org>
	<CB3E86CE-5A05-43B4-81AC-443B727F14D4@cisco.com>
	<6D1FB7A5-37E0-4708-A0F7-61B05251BFE4@g11.org.uk>
	<0879C74D-31CA-4F54-BC6D-1B8BC0F44B50@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1AC06006-FD5D-47B9-A839-B920241148FB@cisco.com>
Content-Transfer-Encoding: 7bit
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Date: Wed, 1 Aug 2007 12:01:04 +0200
To: ken carlberg <carlberg@g11.org.uk>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 01 Aug 2007 10:04:03.0348 (UTC)
	FILETIME=[49FB0540:01C7D423]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3967; t=1185962645;
	x=1186826645; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.com>
	|Subject:=20draft-ietf-tsvwg-rsvp-proxy-proto-approaches
	|Sender:=20; bh=FunsUYKhuYkCwI672uk8J4Qj5BNuqFLz660QAYerN0I=;
	b=e+kLSxaRepEjs2ajDusaE1Wgz3TGtwRMSfZm0lGR2RMSTIMcPCio9SCONCLb/ADkmeTWp1Ui
	weQmW2Ew8pl7IR1rg1qUWwo06MK62lzndfNxMjuC6JeBa+mR0asbjJsS;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: tsvwg tsvwg <tsvwg@ietf.org>
Subject: [Tsvwg] draft-ietf-tsvwg-rsvp-proxy-proto-approaches
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Ken,

>
>>
>> 5) Finally, this may be a nit, but it might be helpful to add a  
>> Considerations section at the end of the document that mentions  
>> the possible scenario of proxy reservations being established and  
>> yet the end-host destination being unreachable/non-existent?   
>> Proxy RSVP routers will know if the downstream leaf router is  
>> reachable, but they won't necessarily know if the last hop to the  
>> end host is reachable.  And since the proxy segment may be part of  
>> an asymmetric path, one can't rely on upstream data to give a hint  
>> to the proxy receiver that the destination is up.
>>
>> I don't think this is major liability, but just something that  
>> needs to be mentioned to those that choose to deploy this work.
>
> I would say this consideration is not specific to the particular  
> type of RSVP Proxy discussed in this document, but actually  
> applicable to most RSVP Proxy scenario/approaches. So I would  
> suggest we bring this point in the rsvp-proxy-approaches document.
>
> As you say, generally in practice I don't expect this is to be a  
> major concern since application level-signaling would take place  
> with the sender/receiver before RSVP reservations are established,  
> so that if either is unreachable, application signaling will be  
> affected first. But it is conceivable that receiver is reachable  
> from application server and not reachable from sender. So we may as  
> well bring up that point (in proxy-approaches).

Below is the text I drafted to address your comment about un- 
reachability scenarios. It is intended to go into a new section  
(4.9). Let us know if you have any comments.
Thanks

Francois


4.9.  Reachability Considerations

    There may be situations where the RSVP Receiver Proxy is  
reachable by
    the sender, while the receiver itself is not.  In such  
situations, it
    is possible that the RSVP Receiver Proxy is not always aware that  
the
    receiver is unreachable, and consequently may accept to establish an
    RSVP reservation on behalf of that receiver.  This would result in
    unnecessary reservation establishment and unnecessary network
    resource consumption.

    This is not considered a significant practical concern for a number
    of reasons.  First, in many cases, if the receiver is not reachable
    from the sender, it will not be reachable either for application
    signaling so that application level session establishment will  
not be
    possible in the first place.  Secondly, where the receiver is
    unreachable from the sender but is reachable for application level
    signaling (say because session establishment is performed through an
    off-path SIP agent that uses a different logical topology to
    communicate with the receiver), then the sender may detect that the
    receiver is unreachable before attempting reservation establishment.
    This may be achieved through mechanisms such as ICE's connectivity
    check ( [I-D.ietf-mmusic-ice]).  Finally, even if the sender does  
not
    detect that the receiver is unreachable before triggering the RSVP
    reservation establishment, it is very likely that the application
    will quickly realise this lack of connectivity (e.g. the human
    accepting the phone call on the receiver side will not hear the
    human's voice on the sender side) and therefore tear down the  
session
    (e.g. hang up the phone) which in turn will trigger RSVP reservation
    release.

    Nonetheless, it is recommended that network administrators consider
    the above in light of their particular environment when deploying
    RSVP Proxys.

    The mirror considerations apply for situations involving an RSVP
    Sender Proxy and where the sender cannot reach the destination while
    the RSVP Sender Proxy can.



>
> Thanks
>
> FRancois
>
>>
>> -ken
>>
>>
>





From tsvwg-bounces@ietf.org Wed Aug 01 10:14:58 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGEyU-00011s-14; Wed, 01 Aug 2007 10:14:54 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IGEyS-00011K-Mi
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 10:14:52 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGEyS-000119-1R; Wed, 01 Aug 2007 10:14:52 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IGEyR-0000Dx-Dv; Wed, 01 Aug 2007 10:14:51 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	AEF6320422; Wed,  1 Aug 2007 16:14:50 +0200 (CEST)
X-AuditID: c1b4fb3c-b067fbb0000007e1-98-46b0955a7593
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	944EC20011; Wed,  1 Aug 2007 16:14:50 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Aug 2007 16:14:50 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Aug 2007 16:14:50 +0200
Message-ID: <46B0955A.3040900@ericsson.com>
Date: Wed, 01 Aug 2007 16:14:50 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Janet P Gunn <jgunn6@csc.com>
Subject: Re: [Tsvwg] Draft Liaision response to SG13 on
	Emergency	Telecommunications
References: <OF534C1677.A38ACB80-ON85257329.0054CDD0-85257329.005589BA@csc.com>
In-Reply-To: <OF534C1677.A38ACB80-ON85257329.0054CDD0-85257329.005589BA@csc.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Aug 2007 14:14:50.0324 (UTC)
	FILETIME=[52AD5940:01C7D446]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: sip@ietf.org, IETF SIPPING WG <sipping@ietf.org>, tsvwg <tsvwg@ietf.org>,
	NSIS <nsis@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Janet P Gunn skrev:
> 
> Magnus,
> 
> You might want to add-
> 
> draft-polk-tsvwg-signaled-domain-id-00.txt

Well, I want to be somewhat restricted in adding individual work into 
the liaison. Also to me it is not clear how this is applicable in the 
emergency context.

> and
> draft-polk-ecrit-local-emergency-rph-namespace-01.txt
> 

Well, I got another comment about ECRIT WG document which we hadn't 
considered. I will contact the WG chairs and see what they say.

> 
> And maybe
> draft-carlberg-trip-attribute-rp-02

Well, this is in IETF last call currently. So I will put it on my list 
of documents to consider and try to learn more about it.

> 
> My spelling checker says "Liaision" should be "Liaison", but it may be a 
> US centric dictionary.

No, it is Liaison, but I think that error only is in the subject of this 
email.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------





From tsvwg-bounces@ietf.org Wed Aug 01 10:41:10 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGFNp-0004Ao-Mb; Wed, 01 Aug 2007 10:41:05 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IGFNo-00049o-JQ
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 10:41:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGFNn-00049g-Vg; Wed, 01 Aug 2007 10:41:03 -0400
Received: from bay0-omc1-s25.bay0.hotmail.com ([65.54.246.97])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IGFNn-0000GZ-LE; Wed, 01 Aug 2007 10:41:03 -0400
Received: from hotmail.com ([207.46.11.246]) by bay0-omc1-s25.bay0.hotmail.com
	with Microsoft SMTPSVC(6.0.3790.2668); 
	Wed, 1 Aug 2007 07:41:03 -0700
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Wed, 1 Aug 2007 07:41:02 -0700
Message-ID: <BAY124-F38AD2F18676D050BA9A259EAE80@phx.gbl>
Received: from 207.46.11.254 by by124fd.bay124.hotmail.msn.com with HTTP;
	Wed, 01 Aug 2007 14:41:01 GMT
X-Originating-IP: [165.228.132.11]
X-Originating-Email: [li.suozhu@hotmail.com]
X-Sender: li.suozhu@hotmail.com
From: "li suozhu" <li.suozhu@hotmail.com>
To: tsvwg@ietf.org, sigtran@ietf.org
Bcc: 
Date: Wed, 01 Aug 2007 22:41:01 +0800
Mime-Version: 1.0
Content-Type: text/plain; charset=gb2312; format=flowed
X-OriginalArrivalTime: 01 Aug 2007 14:41:02.0844 (UTC)
	FILETIME=[FBF8DBC0:01C7D449]
X-Spam-Score: 2.8 (++)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: 
Subject: [Tsvwg] a query related to multi-homed feature about sctp using vrf
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi All, 

I have a query  related to multi-homed feature about sctp when using vrf.

There are two endpoints ,endpoint-1 and endpoint-2,Endpoint-1 has 2 
interfaces with same IP address but differents vrf( IP1-vrf 1, IP1-vrf2) 
,while endpoint-2 has 2 interfaces with IP2-vrf 1 and IP3-vrf 2 seprately.
In this case ,I want to know what the IPv4 Address Parameter will be ,in 
INIT (endpoint-1 is client)or INIT ACK(endpoint-1 is server) chunk ,Only 
one IPv4 Address or Two same IPv4 Address? and how can a sctp endpoint know 
vrf about a IP address ?

Could someone explain right solution?
 
Best regards,

Li

-----------------------------------------------------------------------

_________________________________________________________________
Ãâ·ÑÏÂÔØ MSN Explorer:   http://explorer.msn.com/lccn/  






From tsvwg-bounces@ietf.org Wed Aug 01 11:15:37 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGFv9-00055r-Ax; Wed, 01 Aug 2007 11:15:31 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IGFv8-00055L-JU
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 11:15:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGFv8-00055D-8J; Wed, 01 Aug 2007 11:15:30 -0400
Received: from gw.openss7.com ([142.179.199.224])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IGFv7-0001sj-O1; Wed, 01 Aug 2007 11:15:30 -0400
Received: from ns.pigworks.openss7.net
	(IDENT:e93cmxuhqEx5puRet+j6L4t40yVVmqj4@ns1.evil.openss7.net
	[192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id l71FFTM23349;
	Wed, 1 Aug 2007 09:15:29 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id l71FFSl09357;
	Wed, 1 Aug 2007 09:15:28 -0600
Date: Wed, 1 Aug 2007 09:15:28 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: li suozhu <li.suozhu@hotmail.com>
Message-ID: <20070801091528.B8495@openss7.org>
Mail-Followup-To: li suozhu <li.suozhu@hotmail.com>, tsvwg@ietf.org,
	sigtran@ietf.org
References: <BAY124-F38AD2F18676D050BA9A259EAE80@phx.gbl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <BAY124-F38AD2F18676D050BA9A259EAE80@phx.gbl>;
	from li.suozhu@hotmail.com on Wed, Aug 01, 2007 at 10:41:01PM
	+0800
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: sigtran@ietf.org, tsvwg@ietf.org
Subject: [Tsvwg] Re: [Sigtran] a query related to multi-homed feature about
	sctp using vrf
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

li,

What's a vrf?

--brian

li suozhu wrote:                                   (Wed, 01 Aug 2007 22:41:01)
> Hi All, 
> 
> I have a query  related to multi-homed feature about sctp when using vrf.
> 
> There are two endpoints ,endpoint-1 and endpoint-2,Endpoint-1 has 2 
> interfaces with same IP address but differents vrf( IP1-vrf 1, IP1-vrf2) 
> ,while endpoint-2 has 2 interfaces with IP2-vrf 1 and IP3-vrf 2 seprately.
> In this case ,I want to know what the IPv4 Address Parameter will be ,in 
> INIT (endpoint-1 is client)or INIT ACK(endpoint-1 is server) chunk ,Only 
> one IPv4 Address or Two same IPv4 Address? and how can a sctp endpoint know 
> vrf about a IP address ?
> 
> Could someone explain right solution?
>  
> Best regards,
> 
> Li

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/





From tsvwg-bounces@ietf.org Wed Aug 01 12:18:53 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGGuM-00022T-To; Wed, 01 Aug 2007 12:18:46 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IGGuK-00020u-3M
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 12:18:44 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGGuH-00020E-R9; Wed, 01 Aug 2007 12:18:41 -0400
Received: from mail130.messagelabs.com ([216.82.250.163])
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IGGuH-0003c1-7H; Wed, 01 Aug 2007 12:18:41 -0400
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-6.tower-130.messagelabs.com!1185985118!10207402!1
X-StarScan-Version: 5.5.12.11; banners=-,-,-
X-Originating-IP: [20.137.52.151]
Received: (qmail 17586 invoked from network); 1 Aug 2007 16:18:39 -0000
Received: from amer-mta07.csc.com (HELO amer-mta07.csc.com) (20.137.52.151)
	by server-6.tower-130.messagelabs.com with AES256-SHA encrypted SMTP;
	1 Aug 2007 16:18:39 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245])
	by amer-mta07.csc.com (Switch-3.1.6/Switch-3.1.7) with ESMTP id
	l71GIqaX015895; Wed, 1 Aug 2007 12:18:54 -0400 (EDT)
In-Reply-To: <46B0955A.3040900@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [Tsvwg] Draft Liaision response to SG13 on
	Emergency	Telecommunications
MIME-Version: 1.0
X-Mailer: Lotus Notes 652HF83 November 04, 2004
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OFF3619E59.61764BDC-ON8525732A.0058A6B2-8525732A.005997A1@csc.com>
Date: Wed, 1 Aug 2007 12:18:34 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 7.0.2FP1
	HF180|March 29, 2007) at 08/01/2007 12:17:15 PM,
	Serialize complete at 08/01/2007 12:17:15 PM
Content-Type: multipart/alternative;
	boundary="=_alternative 0059975B8525732A_="
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: sip@ietf.org, IETF SIPPING WG <sipping@ietf.org>, tsvwg <tsvwg@ietf.org>,
	NSIS <nsis@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is a multipart message in MIME format.
--=_alternative 0059975B8525732A_=
Content-Type: text/plain; charset="US-ASCII"

Magnus Westerlund <magnus.westerlund@ericsson.com> wrote on 08/01/2007 
10:14:50 AM:

> Janet P Gunn skrev:
> > 
> > Magnus,
> > 
> > You might want to add-
> > 
> > draft-polk-tsvwg-signaled-domain-id-00.txt
> 
> Well, I want to be somewhat restricted in adding individual work into 
> the liaison. Also to me it is not clear how this is applicable in the 
> emergency context.

Well, you included draft-polk-sip-rph-new-namespaces-01, and 
draft-polk-tsvwg-signaled-domain-id-00 addresses the same scenarios.  It 
would make sense to include either both or neither.
> 
> > and
> > draft-polk-ecrit-local-emergency-rph-namespace-01.txt
> > 
> 
> Well, I got another comment about ECRIT WG document which we hadn't 
> considered. I will contact the WG chairs and see what they say.

Yes, ecrit should make the call. But I know at least one other stds body (
PacketCable PKT2 0-SP-RSTF-D01-060330 TCHG) is addressing it.

Janet

> 
> Cheers
> 
> Magnus Westerlund
> 
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM/M
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> Torshamsgatan 23           | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------

--=_alternative 0059975B8525732A_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif"><br>
</font>
<br>
<br><font size=2><tt>Magnus Westerlund &lt;magnus.westerlund@ericsson.com&gt;
wrote on 08/01/2007 10:14:50 AM:<br>
<br>
&gt; Janet P Gunn skrev:<br>
&gt; &gt; <br>
&gt; &gt; Magnus,<br>
&gt; &gt; <br>
&gt; &gt; You might want to add-<br>
&gt; &gt; <br>
&gt; &gt; draft-polk-tsvwg-signaled-domain-id-00.txt<br>
&gt; <br>
&gt; Well, I want to be somewhat restricted in adding individual work into
<br>
&gt; the liaison. Also to me it is not clear how this is applicable in
the <br>
&gt; emergency context.</tt></font>
<br>
<br><font size=2><tt>Well, you included draft-polk-sip-rph-new-namespaces-01,
and draft-polk-tsvwg-signaled-domain-id-00 addresses the same scenarios.
&nbsp;It would make sense to include either both or neither.<br>
&gt; <br>
&gt; &gt; and<br>
&gt; &gt; draft-polk-ecrit-local-emergency-rph-namespace-01.txt<br>
&gt; &gt; <br>
&gt; <br>
&gt; Well, I got another comment about ECRIT WG document which we hadn't
<br>
&gt; considered. I will contact the WG chairs and see what they say.</tt></font>
<br>
<br><font size=2><tt>Yes, ecrit should make the call. But I know at least
one other stds body (PacketCable PKT2 0-SP-RSTF-D01-060330 TCHG) is addressing
it.</tt></font>
<br>
<br><font size=2><tt>Janet<br>
<br>
&gt; <br>
&gt; Cheers<br>
&gt; <br>
&gt; Magnus Westerlund<br>
&gt; <br>
&gt; IETF Transport Area Director &amp; TSVWG Chair<br>
&gt; ----------------------------------------------------------------------<br>
&gt; Multimedia Technologies, Ericsson Research EAB/TVM/M<br>
&gt; ----------------------------------------------------------------------<br>
&gt; Ericsson AB &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
Phone +46 8 4048287<br>
&gt; Torshamsgatan 23 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Fax &nbsp; +46
8 7575550<br>
&gt; S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com<br>
&gt; ----------------------------------------------------------------------<br>
</tt></font>
--=_alternative 0059975B8525732A_=--





From tsvwg-bounces@ietf.org Wed Aug 01 12:31:30 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGH6d-000108-O1; Wed, 01 Aug 2007 12:31:27 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IGH6c-0000zz-Nm
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 12:31:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGH6c-0000zr-0J; Wed, 01 Aug 2007 12:31:26 -0400
Received: from exprod7og52.obsmtp.com ([64.18.2.159])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IGH6a-00039b-NB; Wed, 01 Aug 2007 12:31:25 -0400
Received: from source ([67.96.16.12]) (using TLSv1) by exprod7ob52.obsmtp.com
	([64.18.6.12]) with SMTP; Wed, 01 Aug 2007 09:31:14 PDT
Received: from ETSMSG-CINAV02.etsmsg.org ([65.90.82.49]) by
	naout-cinexs02.nasmtpout.emrsn.com with Microsoft
	SMTPSVC(6.0.3790.3959); Wed, 1 Aug 2007 12:43:01 -0400
Received: from etsmsg-cinexs03.etsmsg.org ([65.90.82.49]) by
	ETSMSG-CINAV02.etsmsg.org with InterScan Message Security Suite;
	Wed, 01 Aug 2007 12:31:14 -0400
Received: from ETSMSG-CINEXR02.etsmsg.org ([65.90.82.108]) by
	etsmsg-cinexs03.etsmsg.org with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 1 Aug 2007 12:31:13 -0400
Received: from USACG-MSNEXM01.astec.com ([10.206.84.182]) by
	ETSMSG-CINEXR02.etsmsg.org with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 1 Aug 2007 12:31:12 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="GB2312"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Tsvwg] a query related to multi-homed feature about sctp using
	vrf
Date: Wed, 1 Aug 2007 11:31:09 -0500
Message-ID: <DB255B459C0A1C458EB2D2353F1269CB0304E8C0@USACG-MSNEXM01.astec.com>
In-Reply-To: <BAY124-F38AD2F18676D050BA9A259EAE80@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tsvwg] a query related to multi-homed feature about sctp using
	vrf
Thread-Index: AcfUSgG1bz2GP6hkRiy/jXSS85ChtQADyElg
From: <ronnie@artesyncp.com>
To: <li.suozhu@hotmail.com>,
	<tsvwg@ietf.org>,
	<sigtran@ietf.org>
X-OriginalArrivalTime: 01 Aug 2007 16:31:12.0066 (UTC)
	FILETIME=[5F601A20:01C7D459]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

If there is only one IP address at an endpoint that endpoint is single =
homed as far as SCTP is concerned.  Only one IP address (if any) would =
be listed in it's INIT or INIT ACK chunks.  SCTP knows nothing about =
interfaces.

Ronnie

---
Ronnie Sellar			Emerson Network Power, Embedded Computing
Tel: +44 131 475 7015		Suite 4, 2 Anderson Place
Fax: +44 131 475 7001		Edinburgh EH6 5NP
mailto:ronnie@artesyncp.com	http://www.emersonembeddedcomputing.com
=20

> -----Original Message-----
> From: li suozhu [mailto:li.suozhu@hotmail.com]=20
> Sent: 01 August 2007 15:41
> To: tsvwg@ietf.org; sigtran@ietf.org
> Subject: [Tsvwg] a query related to multi-homed feature about=20
> sctp using vrf
>=20
> Hi All,=20
>=20
> I have a query  related to multi-homed feature about sctp=20
> when using vrf.
>=20
> There are two endpoints ,endpoint-1 and endpoint-2,Endpoint-1=20
> has 2 interfaces with same IP address but differents vrf(=20
> IP1-vrf 1, IP1-vrf2) ,while endpoint-2 has 2 interfaces with=20
> IP2-vrf 1 and IP3-vrf 2 seprately.
> In this case ,I want to know what the IPv4 Address Parameter=20
> will be ,in INIT (endpoint-1 is client)or INIT ACK(endpoint-1=20
> is server) chunk ,Only one IPv4 Address or Two same IPv4=20
> Address? and how can a sctp endpoint know vrf about a IP address ?
>=20
> Could someone explain right solution?
> =20
> Best regards,
>=20
> Li
>=20
> --------------------------------------------------------------
> ---------
>=20
> _________________________________________________________________
> =C3=E2=B7=D1=CF=C2=D4=D8 MSN Explorer:   http://explorer.msn.com/lccn/ =
=20
>=20
>=20
>=20
>=20





From tsvwg-bounces@ietf.org Wed Aug 01 12:59:57 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGHY7-0005uG-UG; Wed, 01 Aug 2007 12:59:51 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IGHY6-0005u2-VM
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 12:59:50 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IGHY6-0005tp-J1
	for tsvwg@ietf.org; Wed, 01 Aug 2007 12:59:50 -0400
Received: from dee.erg.abdn.ac.uk ([139.133.204.82] helo=erg.abdn.ac.uk)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGHY5-0004gM-6t
	for tsvwg@ietf.org; Wed, 01 Aug 2007 12:59:50 -0400
Received: from [10.10.10.232] (fgrpf.plus.com [212.159.18.54])
	(authenticated bits=0)
	by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id l71GuOJx000633
	(version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT);
	Wed, 1 Aug 2007 17:56:35 +0100 (BST)
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Wed, 01 Aug 2007 17:56:24 +0100
Subject: Re: [Tsvwg] ECN with Tunnels - to copy or change the ECN in the
	outerheader
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Message-ID: <C2D679C8.7A0D%gorry@erg.abdn.ac.uk>
Thread-Topic: [Tsvwg] ECN with Tunnels - to copy or change the ECN in the
	outerheader
Thread-Index: AcfUXOSOIwPIM0BQEdyW2wAKlc/qXg==
In-Reply-To: <5.2.1.1.2.20070731215135.04a04098@pop3.jungle.bt.co.uk>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
X-Spam-Status: No
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 155726d2f5fe5eb5c40a9f079fd9e841
Cc: "BLACK, David" <Black_David@emc.com>, tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


Responding to David and Bob together,

On 1/8/07 01:50, "Bob Briscoe" <rbriscoe@jungle.bt.co.uk> wrote:

> Gorry,
> 
> At 03:42 30/07/2007, Black_David@emc.com wrote:
>> Gorry,
>> 
>>> [GF]: I have a query about the draft on ECN use with Tunnels, relating to
>>> the ECN codepoint copying that I raised in the TSV meeting yesterday.
>>> 
>>> As I understand, the adjustment to IPsec related only to copying the 2
>>> ECN bits (plus DS codepoints) from the outer to the inner on ingress and
>>> back again at egress. I agree we SHOULD also do a similar recommendation
>>> for Tunnels in general, and I'd like to see this STD-Track for use in the
>>> General Internet.
>> 
>> [DB]: IPsec (RFC 4301) does something slightly different on egress - it only
>> copies a CE codepoint from outer to inner.
> 
> [BB]: I deliberately kept the behaviour at the egress unchanged from
> RFC3168 ECN and RFC4301 IPsec (except I added some "MAY warn" statements
> for illegal transitions).
> 
OK

>>> [GF]: However, I am concerned that this draft does not only address these
>>> problems (which could be a PS), but it also adds new concepts as well.
>>> 
>>> In the ECN architecture, my understanding is that HOSTs choose to set the
>>> ECN field to ECT(0) and ECT(1), depending upon the policy at the sender.
> 
> [BB]: FYI,  somewhere around the time the ECN spec was in the last stages
> of becoming RFC3168 in early 2001, I discussed with Sally the possibility
> of in-path nodes ('proxies') setting ECT (I think it was off-list, but I
> believe I summarised the conversation to the list). Sally's sensible view
> was that any such behaviour would have to be defined at the time such a
> proxy was defined. That's essentially what the PCN w-g is doing now (back
> then, we were working on what has become PCN, which is why I had an interest).
> 
I haven't seen a discussion of this in the context of general internet use
for tunnels. I know that the ECN work includes these ideas within a
"domain".

>>> [GF]: ECN Nonce ( RFC3540) implies a specific semantic to this. The IETF
>>> has a BCP that also says how other alternative semantics may be applied
>>> with specific DS codepoints (RFC4774).
>>> 
>>> There seem to be two new ideas here. While this may be being considered
>>> in other places, I do not recall it as a part of the original design for
>>> ECN:
>>> 
>>> * The idea that packets from an end host that do not use an ECN-capable
>>> transport can be mapped to an ECT codepoint over a congestion-controlled
>>> tunnel. The current scope of this work in the IETF seems to be scoped
>>> only for use within a PCN domain.
>> 
>> [DB]: I tend to agree.  Absent something like PCN that invokes alternate
>> semantics for the ECN field, the congestion control for the tunnel would
>> have to be TCP-like (reaction to congestion-marked packet is equivalent to
>> reaction to dropped packet) in order to comply with RFC 3168.
> 
> [BB]: I relegated the stuff about an in-path load regulator to an appendix
> because I didn't want to introduce new stuff, but I did want to somehow
> give advice relevant to the PCN w-g (and possibly PWE3 and CAPWAP who are
> both knocking around ideas about in-path load regulators).
> 
> In-path load regulation is often a bad idea, but I didn't want to make that
> judgement in this draft, which is just about how tunnels handle the wire
> protocol. So I wanted to keep it at the level of "In any cases where the
> IETF deems in-path load regulation is sensible, this is what you should do
> with the wire protocol, if the load regulator co-incides with a tunnel
> ingress."
> 
> Just before the Chicago IETF, as David says, I realised I'd got the stuff
> about in-path load regulators wrong anyway. I now believe that an in-path
> load regulator would reset CE to ECT *before* any tunnel encapsulation.
> 
> I *think* these second thoughts mean that in-path load regulation is
> orthogonal to tunnelling, so I can just remove it from this draft
> altogether. And it can be dealt with in the relevant w-g (e.g. PCN, PWE3 or
> CAPWAP).
> 
> But I'd like to allow myself third thoughts when I update to -01. At that
> time, if I leave anything in about in-path load regulators I'll pop it onto
> the list first to get your reaction (and others).
>
So, this is draft -00, I'd be interested to see how this develops.

>>> [GF]: * The idea that packets marked with an ECN codepoint may be
>>> remarked to a different ECN codepoint by some tunnel endpoints, including
>>> mapping CE to an ECT value, and mapping ECT(1) to ECT(0).
>>> 
>>>   "If the tunnel ingress is also a Load Regulator, it MUST instead reset
>>>    the outer header to ECT(0)."
> 
> [BB]: Strictly, this idea isn't new. It was the full functionality mode in
> RFC3168. The CE is preserved through the inner header and pops out the
> other end of the tunnel, whatever variant of egress behaviour it encounters.
> 
Right.

An alternative could be that the tunnel could copy ECT(0), ECT(1), & CE to
the outer header (and update 00 to some codepoint such as ECT(0), which
seems to better preserve some types of semantics, I wonder which causes
fewest issues (would the assumption be that DSCP was also copied?)

> However, you are right that the idea of an in-path load regulator doing
> this is new (but likely to be removed anyway - so lets not worry about it
> for now).
> 
Aha.

>>> [GF]: Section 7:
>>>   "The rule that a tunnel ingress MUST copy any ECN field into the outer
>>>    header is a change to RFC3168 (unless it is a Load Regulator as well, in
>>>    which case there is no change)."
>> 
>> [DB]: Bob and I have had some serious private discussions about this.
>> IMHO, the charitable conclusion is that the Load Regulator
>> concept in the draft has not been completely thought through
>> (after all, it is a "draft"), and I believe Bob is considering
>> just dropping it from the next version of this draft.
>> 
>>> [GF]: The draft describes permitting a mid-box/router to choose to reset the
>>> code point to ECT(0) when it was originally set to some other value.
>>> 
>>> - So my view on this varies depending on the original value:
>>> N-ECT  -> ECT(0) ... I think this was the goal,
>>>                    but is this safe in the general internet?
>> 
>> [DB]: Provided that the tunnel ingress *knows* that the tunnel egress
>> will do the "right thing" (e.g., drop if outer is marked with CE,
>> else forward with N-ECT from inner header) this should be ok, but
>> *knows* can't just be *assumes*.  This is headed in the interesting
>> direction of running a congestion control feedback loop from tunnel
>> ingress to egress in a fashion transparent to the end-to-end
>> congestion control.  There are some details to watch out for, as
>> a drop could activate both ingress-to-egress and end-to-end
>> congestion control.
> 
> [BB]: I agree with David here.
> 
Fine with me.

>>> [GF]:
>>> ECT(0) -> ECT(0) ... No change
>>> ECT(1) -> ECT(0) ... This contradicts  RFC3540 and RFC4774, and seems
>>>                    like we are limiting options for using schemes
>>>                    currently permitted and options for the future.
>> 
>> [DB]: Hmm ... I have the impression that non-support for 3540 (experimental)
>> is "in play" as a potential part of PCN.
>>
?? Hmmmm ??

>> FWIW, 4301 (IPsec) tunneled
>> the 3540 nonce rather than propagating it through the outer header.
>> Beyond this, I can't agree with the "contradicts ... RFC 4774"
>> statement without a much longer discussion ;-).


> [BB]: As I point out in the security considerations section of this draft,
> RFC3168 tunnel behaviour currently complicates the ECN nonce anyway, losing
> the sender's nonce protection over the length of the tunnel (noting Sally's
> point in the previous mail that the tunnel egress could detect changes to
> the nonce in these cases). Ideally, I would have redefined the egress
> behaviour to fix this, but I left it as it is, to avoid changing IPsec again.
> 
> We could fix the nonce as well, using this draft. But in discussions with
> David B, Bruce Davie and separately with the Transport ADs, the proposed
> plan is to wait until PCN is more mature, then we can take everything that
> might need taking into account, all together.
> 
> Current plan is to issue an update to this draft, still as individual
> draft-briscoe-tsvwg-ecn-tunnel-01 to make some necessary corrections to
> this draft that don't depend on where PCN might go, but then leave the I-D
> on hold for at least one IETF cycle to allow us to identify any consensus
> the PCN w-g is converging on regarding header encoding.
> 
I'll look at the next rev.

> [BTW, PCN doesn't need to support the nonce edge-edge because PCN boundary
> nodes don't do predictable edge-edge packet ordering so a binary nonce
> wouldn't work anyway (but PCN may have to preserve an e2e nonce by
> tunnelling the e2e header - this is how I would approach the possibility of
> end-to-end having to coexist with edge-to-edge control loops).]
>
I don't understand the ordering with nonce issue, but that's a different
topic.

>>> [GF]:
>>> CE    -> ECT(0) ... What are the implications of this when transiting
>>>                    a network using ECN or alt. ECN semantics?
> 
> [BB]: This is the way RFC3168 worked: full functionality mode reset CE ->
> ECT(0) at tunnel ingress and ignored which ECT value was in the outer
> header at the egress, instead reinstating the ECT values from the inner
> header.
> 
OK, but since then we have seen protocols using both ECT(0) and ECT(1).
Nonce and others (with a DSCP), so I was hoping these could work with
tunnels (at least within the domains were they were to be used).

>> [DB]: As long as CE is tunneled through the inner header and not overwritten
>> at tunnel egress (i.e., end receiver gets CE, not ECT(0) in received
>> packet), this should be ok, as a router that would otherwise set CE
>> doesn't do anything different with a packet that is already marked
>> with CE vs. just marked with ECT.  Dropping a CE-packet doesn't change
>> the reaction of a correct end-system and is not helpful to a correct
>> end-system.
> 
Yes, except if ECT(0) and ECT(1) had mean something for a flow, then  CE
means it was once one of these, (but the devices can not know which).

> [BB]: A final process note:
> 
> As I said in the presentation last week, this draft currently aims to serve
> two purposes that I believe can both sit in one doc intended for PS:
> 1) A PS to bring 3168 into line with 4301
> 2) Informational guidance on the tunnelling constraints to consider
> if  defining new ECN field semantics for certain DS PHBs (like PCN) or for
> integrating IP congestion notification with lower layer protocols.
> 
> This leads to a potential for gridlock (or a race condition) with the PCN
> working group...
> 
> It would be wrong to bring RFC3168 into line with RFC4301 *before* PCN has
> decided its encoding, just in case there is something we can say in this
> ecn-tunnel doc that would ensure all tunnels 'just work' without special
> PCN modifications. IOW, the IETF needs to avoid the possibility of making
> two changes in quick succession to ECN tunnelling. Otherwise, the
> intermediate stage would create yet another tunnel endpoint variant that
> corresponding tunnel endpoints would have to check for.
> 
Agreed, not a good result.

> But I wanted to have the guidance written down to improve the chances of
> the PCN w-g defining an encoding (chartered to be delivered to the IESG by
> Mar'08) so that tunnels would indeed 'just work' without special PCN
> modifications.
> 
> Even if I had split this draft into informational and PS parts, the PCN w-g
> need the informational part before Oct'07 for it to be useful. So, is it a
> reasonable approach to get the guidance in as good a shape as possible
> (thru discussions like this on the list) while still remaining as an
> individual draft? Then the PCN w-g can note the guidance in the knowledge
> it might be useful, but it is not fully baked or even formally adopted by
> the IETF. Thus relaxing the potential for gridlock.
> 
> Hope this helps.
> 
> Cheers
> 
> 
> Bob
> 
> 
> ____________________________________________________________________________
> Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
> B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196
> 

Great to see someone working on these issues, thanks Bob!

Gorry








From tsvwg-bounces@ietf.org Wed Aug 01 13:57:51 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGIRF-0002Pu-2t; Wed, 01 Aug 2007 13:56:49 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IGIRE-0002Pl-EJ
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 13:56:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGIRE-0002Pd-2V; Wed, 01 Aug 2007 13:56:48 -0400
Received: from rwcrmhc14.comcast.net ([216.148.227.154])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IGIRC-0005Hk-6e; Wed, 01 Aug 2007 13:56:47 -0400
Received: from macbookpro.lei.chicago.il.us
	(c-67-167-15-209.hsd1.il.comcast.net[67.167.15.209])
	by comcast.net (rwcrmhc14) with ESMTP
	id <20070801175643m14003balhe>; Wed, 1 Aug 2007 17:56:44 +0000
Message-ID: <46B0C93B.5030905@ieee.org>
Date: Wed, 01 Aug 2007 12:56:11 -0500
From: Peter Lei <peter.lei@ieee.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US;
	rv:1.8.1.5) Gecko/20070719 SeaMonkey/1.1.3 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: li suozhu <li.suozhu@hotmail.com>
Subject: Re: [Tsvwg] a query related to multi-homed feature about sctp using
	vrf
References: <BAY124-F38AD2F18676D050BA9A259EAE80@phx.gbl>
In-Reply-To: <BAY124-F38AD2F18676D050BA9A259EAE80@phx.gbl>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: sigtran@ietf.org, tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

SCTP itself is unaware of VRFs (as is the case for TCP and UDP).   The
addresses sent within the protocol are interface agnostic.

However, you can extend the SCTP stack and applications to be VRF-aware
and we do have an implementation that allows this; we have extended the
API (in a implementation specific manner) to support VRFs.

If you can make the assumption that an association will belong to one and
only one VRF (which I think is an appropriate assumption), the INIT/INIT-ACK
chunks will only list the addresses that are part of the VRF.  Thus in
this case,
you would never list the same IP address more than once.

When responding to incoming packets, you will need to get the appropriate
VRF identifier from your OS/IP stack on a per-packet basis; this can be an
explicit VRF identifier or a mapping of some ingress interface
identifier to a
specific VRF.  Similarly on the egress side, you would likely need to
pass an
explicit VRF identifier to the OS/IP stack, or need to select an appropriate
egress interface (corresponding to the addresses sent in the INIT/INIT-ACK).

--peter


li suozhu wrote:
> Hi All,
> I have a query  related to multi-homed feature about sctp when using vrf.
> 
> There are two endpoints ,endpoint-1 and endpoint-2,Endpoint-1 has 2 
> interfaces with same IP address but differents vrf( IP1-vrf 1, IP1-vrf2) 
> ,while endpoint-2 has 2 interfaces with IP2-vrf 1 and IP3-vrf 2 seprately.
> In this case ,I want to know what the IPv4 Address Parameter will be ,in 
> INIT (endpoint-1 is client)or INIT ACK(endpoint-1 is server) chunk ,Only 
> one IPv4 Address or Two same IPv4 Address? and how can a sctp endpoint 
> know vrf about a IP address ?
> 
> Could someone explain right solution?
> 
> Best regards,
> 
> Li
> 
> -----------------------------------------------------------------------
> 
> _________________________________________________________________
> Ãâ·ÑÏÂÔØ MSN Explorer:   http://explorer.msn.com/lccn/ 
> 
> 
> 





From tsvwg-bounces@ietf.org Wed Aug 01 18:17:01 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGMUo-0001mr-DH; Wed, 01 Aug 2007 18:16:46 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IGMUn-0001mm-68
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 18:16:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IGMUm-0001me-Qn
	for tsvwg@ietf.org; Wed, 01 Aug 2007 18:16:44 -0400
Received: from smtpout.mac.com ([17.250.248.184])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGMUl-0004lV-V4
	for tsvwg@ietf.org; Wed, 01 Aug 2007 18:16:44 -0400
Received: from mac.com (smtpin05-en2 [10.13.10.150])
	by smtpout.mac.com (Xserve/smtpout14/MantshX 4.0) with ESMTP id
	l71MGcPD001904; Wed, 1 Aug 2007 15:16:43 -0700 (PDT)
Received: from [192.150.186.170] (laptop170.icsi.berkeley.edu
	[192.150.186.170]) (authenticated bits=0)
	by mac.com (Xserve/smtpin05/MantshX 4.0) with ESMTP id l71MGaIW023797; 
	Wed, 1 Aug 2007 15:16:36 -0700 (PDT)
In-Reply-To: <5.2.1.1.2.20070731234936.04a65eb8@pop3.jungle.bt.co.uk>
References: <5.2.1.1.2.20070731234936.04a65eb8@pop3.jungle.bt.co.uk>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <db506707967feeedb704118ece0639c5@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Date: Wed, 1 Aug 2007 15:16:34 -0700
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
X-Mailer: Apple Mail (2.624)
X-Brightmail-Tracker: AAAAAA==
X-Brightmail-scanned: yes
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: tsvwg WG <tsvwg@ietf.org>
Subject: [Tsvwg] Re: feedback on draft-briscoe-tsvwg-ecn-tunnel-00
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Bob -

This is a long email, but it just says "OK" in response to email from 
Bob
about two small wording issues, and continues an extended but
non-critical discussion about one case of "MUST" vs. "SHOULD".  FYI...


>> So ECN was designed with transport protocols in mind, but it was not
>> designed only for unicast, TCP-like transport protocols.  In 
>> particular,
>> there could be protocols where the transport receiver is the actor,
>> not the transport sender.
>
> Good point. How about...
>
> "ECN at the IP layer is designed to carry information about congestion
> from a congested resource towards downstream nodes. Typically a 
> downstream transport might feed the information back somehow to the 
> point upstream of the congestion that can regulate the load on the 
> congested resource, but other actions are possible (see [RFC3168] 
> Sec.6)."

That sounds fine to me.


>> Section 3.2:
>> "It might be useful for the tunnel egress to be able to tell whether
>> congestion occurred across a tunnel or upstream of it."
>>
>> The rest of the paragraph is specific to multi-level congestion
>> marking such as PCN (and even in this case, I assume that the tunnel
>> egress can only tell whether congestion occurred across the tunnel
>> or upstream of it if the ECN field was not already at the highest
>> of the multi levels at tunnel ingress).
>>
>> It seems *conceivable* to me that someone might want to design a
>> tunnel where the egress would want to know whether congestion
>> occurred across the tunnel or upstream of it, but where the ingress
>> was not a Load Regulator.  (I don't know why, offhand, though
>> multicast comes to mind.)  *If* one wanted to allow this in some
>> future tunnel, then one should change the MUST about copying the
>> ECN field from the inner to the outer header at ingress to a SHOULD.
>> And if one didn't want to allow this, then this should be made as
>> explicit as possible, I would say.  Making it completely clear that
>> when the ECN field is copied from the inner to the outer header at
>> ingress, then the tunnel egress won't necessarily be able to tell
>> whether congestion occurred across a tunnel or upstream of it.
>> (I guess that a simple way out would be just to stretch the
>> definition of "Load Regulator", to say that any time the tunnel
>> egress wants to be able to tell whether congestion occurred
>> across the tunnel or upstream of it, the ingress is called a
>> Load Regulator.)
>
> Actually, I think you'll find the rest of the para isn't specific to 
> PCN and it answers your question (particularly from "But the same 
> information could be gleaned...").

As I read it, the rest of that paragraph is specific to
multi-level congestion marking.

> Essentially, even if the ingress copies the incoming header to the 
> outer, any _additional_ marking along the tunnel can be detected at 
> the tunnel egress as a difference between inner & outer.

Yep.  But *additional* marking (for an ECN codepoint defined to
have multi-level congestion, and for a packet that is not already
marked at the highest level of congestion before the tunnel ingress)
is one thing, and a packet that *would have been* marked in
the tunnel if it hadn't already been marked is another.
I think it is good to be quite clear about the difference.

> Having realised this, there was no reason not to say MUST as:
> - a single behaviour is always preferable to multiple options

I happen to disagree.  The guideline that I use is not to specify
"MUST" unless I think it is necessary.  I don't know off-hand if there
is a specific IETF guideline on this.

> - and copying at ingress actually doesn't lose info that might one day 
> be useful about what happened across the tunnel.

And I said above, I think this is wrong.  I think that copying at
ingress is fine.  But I think it is good to be clear that is *does*
lose information about routers that would have marked packets along
the tunnel (e.g., for the default ECN semantics specified in RFC 3168,
or for packets that were already marked at the highest level in a
multi-level congestion mechanism).

> Strictly, additional marking isn't quite the same as additional 
> congestion (additional congestion which might have just happened to 
> mark the same packet as was already marked). But, I don't think we 
> should start introducing complicating options to allow for this corner 
> case within some possible future scheme to extract what happened 
> within the tunnel, that we're not sure anyone will ever want anyway. 
> That corner case might be important to some scheme in the future 
> during high congestion, but I suggest it will be their task to change 
> MUST to SHOULD if they really need to.

I would prefer "SHOULD", but I could live with "MUST".  But if the
draft leaves it as MUST, then I think the draft should clarify that
this means that the tunnel egress can't necessarily tell if a router
in the tunnel would have marked the packet, because it is quite
possible that the packet was already marked at the highest marking
level before it entered the tunnel.   I would also suggest that
the draft clarify that if someone in the future wanted to use
a tunnel protocol where the egress router can detect whether packets
are marked inside the tunnel, then they would have to change this
"MUST" to a "SHOULD" or "MAY".

...
> Nits:
>> From the abstract:
>> This document "gives general principles to guide the design of
>> alternate congestion marking behaviours for specific PHBs and for
>> lower layer congestion notification schemes."
>>
>> Where did this document do that?  That seems misleading to me.
>
> I meant "... gives general principles to guide the design of 
> tunnelling behaviours for alternate congestion marking schemes used by 
> specific PHBs, and and the design of encapsulations by lower layer 
> headers supporting congestion notification."
>
> That's what sections 3 & 4 were meant to do. Is this better?

Yep.  Many thanks.


- Sally
http://www.icir.org/floyd/






From tsvwg-bounces@ietf.org Thu Aug 02 04:26:30 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGW0j-0003PA-Pi; Thu, 02 Aug 2007 04:26:21 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IGW0i-0003K2-NV
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 02 Aug 2007 04:26:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IGW0h-0003GY-GI
	for tsvwg@ietf.org; Thu, 02 Aug 2007 04:26:20 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGW0g-0001Tw-F3
	for tsvwg@ietf.org; Thu, 02 Aug 2007 04:26:18 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 02 Aug 2007 01:26:17 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAPYxsUarR7MV/2dsb2JhbACvYg
X-IronPort-AV: i="4.19,211,1183359600"; 
	d="scan'208"; a="192983459:sNHT24100173"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l728QHuq016928
	for <tsvwg@ietf.org>; Thu, 2 Aug 2007 01:26:17 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l728QHed006606
	for <tsvwg@ietf.org>; Thu, 2 Aug 2007 08:26:17 GMT
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.1830); 
	Thu, 2 Aug 2007 01:26:17 -0700
Received: from jmpolk-wxp.cisco.com ([10.21.119.77]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Aug 2007 01:26:16 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 02 Aug 2007 03:26:15 -0500
To: tsvwg <tsvwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <XFE-SJC-212carcR4ZD00001fe0@xfe-sjc-212.amer.cisco.com>
X-OriginalArrivalTime: 02 Aug 2007 08:26:17.0243 (UTC)
	FILETIME=[CBEC2EB0:01C7D4DE]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=513; t=1186043177;
	x=1186907177; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jmpolk@cisco.com;
	z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com>
	|Subject:=20TSVWG=20*rough/draft*=20minutes |Sender:=20;
	bh=hw3+yATqqcUReERJuvZzrCqrKDGxqHR0o+UTDK2Hlzk=;
	b=V87VdHyFa4DJ43lDs4sn+XckoLHnGEldUKgk0Q+Cg8k9JXvalaNPxQK2GLKDWmJOXIUXn9Qx
	YKlHEY+ZNirwwPIPVEnb9bzy/elLpnB6D2r0hSzitqLwPpOjQxQqKcn85eG7LJdw9zNlCEohKK
	GDhKo1VN+YRJiGMt1mqxr4ocI=;
Authentication-Results: sj-dkim-1; header.From=jmpolk@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: [Tsvwg] TSVWG *rough/draft* minutes
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

TSVWG

Here is the initial set of meeting minutes from IETF69 (Chicago)

         http://www3.ietf.org/proceedings/07jul/minutes/tsvwg.txt

I have not incorporated all the minutes sent to me yet, so the 
minutes will change over the coming weeks. I wanted to get these out 
for early review to help in their refinement.

Comments are appreciated


Cheers,
James
IETF TSVWG co-chair

              ***********************************
     "It should NEVER be inconvenient to do the right thing"





From tsvwg-bounces@ietf.org Thu Aug 02 04:50:21 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGWNm-0006UR-0c; Thu, 02 Aug 2007 04:50:10 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IGWNk-0006Tf-DT
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 02 Aug 2007 04:50:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGWNj-0006SZ-V9; Thu, 02 Aug 2007 04:50:08 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IGWNj-0002JT-8y; Thu, 02 Aug 2007 04:50:07 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	455D52071D; Thu,  2 Aug 2007 10:50:06 +0200 (CEST)
X-AuditID: c1b4fb3e-b0034bb0000007e1-aa-46b19abe2e83
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1E4DB2133C; Thu,  2 Aug 2007 10:50:06 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Aug 2007 10:50:05 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Aug 2007 10:50:05 +0200
Message-ID: <46B19ABC.9080909@ericsson.com>
Date: Thu, 02 Aug 2007 10:50:04 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: Dale.Worley@comcast.net
References: <46AF5370.9020304@ericsson.com>
	<200708012031.l71KVZBv016565@dragon.ariadne.com>
In-Reply-To: <200708012031.l71KVZBv016565@dragon.ariadne.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
X-OriginalArrivalTime: 02 Aug 2007 08:50:05.0234 (UTC)
	FILETIME=[1F125120:01C7D4E2]
X-Brightmail-Tracker: AAAAAA==
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: sip@ietf.org, sipping@ietf.org, tsvwg@ietf.org, nsis@ietf.org
Subject: [Tsvwg] Re: [Sip] Draft Liaision response to SG13 on
	Emergency	Telecommunications
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Dale.Worley@comcast.net skrev:
>    This is a response to the liaison request made by Q3/13 regarding=20
>=20
> It looks like that should be "Q.3/13".
>=20
>    emergency telecommunications (REF: NGN-GSI/DOC =E2=80=93 60 Rev.2). =
We would=20
>    first like to apologize for failing to meet the deadline in respondi=
ng.=20
>    We do hope that the late answer still can be of some use.
>=20
>    The liaison request was made to the following working groups (WG):=20
>    IEPREP, TSVWG, and NSIS. Since the request was sent the IEPREP WG ha=
s=20
>    concluded. In addition to the WGs from which information was request=
ed,=20
>    we also think that work performed by the SIP and SIPPING WG may be o=
f=20
>    relevance.
>=20
>    Pursuant to ITU-T Study Group 13 request for information on relevant=
 and=20
>    related work in the IETF regarding emergency communications, we list=
=20
>    below RFCs and works in progress that we feel may be of interest to =
your=20
>    group.  Some of the completed work is Informational, and others are =
in=20
>    the category of Standards Track.
>=20
>    Q.3/13 also requested that we keep you informed of any developments =
in=20
>    regards to emergency telecommunications. In those regards we would l=
ike=20
>    to make you aware that IETF mailing list participation and document=20
>    information is free and open for anyone. Allowing participants in Q.=
3/13=20
>=20
> "... free and open to anyone, allowing ..."
>=20
>    to keep them selves informed of any developments. If Q.3/13 desire t=
o=20
>=20
> "... themselves ..." (unless that's a US-ism)
>=20
>    get further information about specific ongoing work, then please sen=
d a=20
>    liaison request to the responsible WG for those specific documents.
>=20
>    The following list is divided under the associated working groups fr=
om=20
>    which the work has been done within the IETF.
>=20
> Dale
>=20
Thanks,

incorporated.

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------





From tsvwg-bounces@ietf.org Thu Aug 02 08:33:48 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGZs7-0002Oq-Ka; Thu, 02 Aug 2007 08:33:43 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IGKr4-00049E-Kf
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 16:31:38 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGKr4-000492-9e; Wed, 01 Aug 2007 16:31:38 -0400
Received: from alnrmhc14.comcast.net ([206.18.177.54])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IGKr3-0002Vr-T8; Wed, 01 Aug 2007 16:31:38 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42])
	by comcast.net (alnrmhc14) with ESMTP
	id <20070801203136b1400pgtsle>; Wed, 1 Aug 2007 20:31:37 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1])
	by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l71KVZ8t016569;
	Wed, 1 Aug 2007 16:31:35 -0400
Received: (from worley@localhost)
	by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l71KVZBv016565;
	Wed, 1 Aug 2007 16:31:35 -0400
Date: Wed, 1 Aug 2007 16:31:35 -0400
Message-Id: <200708012031.l71KVZBv016565@dragon.ariadne.com>
From: Dale.Worley@comcast.net
To: magnus.westerlund@ericsson.com
In-reply-to: <46AF5370.9020304@ericsson.com> (magnus.westerlund@ericsson.com)
References: <46AF5370.9020304@ericsson.com>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
X-Mailman-Approved-At: Thu, 02 Aug 2007 08:33:42 -0400
Cc: sip@ietf.org, sipping@ietf.org, tsvwg@ietf.org, nsis@ietf.org
Subject: [Tsvwg] Re: [Sip] Draft Liaision response to SG13 on Emergency
	Telecommunications
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

   This is a response to the liaison request made by Q3/13 regarding 

It looks like that should be "Q.3/13".

   emergency telecommunications (REF: NGN-GSI/DOC â€“ 60 Rev.2). We would 
   first like to apologize for failing to meet the deadline in responding. 
   We do hope that the late answer still can be of some use.

   The liaison request was made to the following working groups (WG): 
   IEPREP, TSVWG, and NSIS. Since the request was sent the IEPREP WG has 
   concluded. In addition to the WGs from which information was requested, 
   we also think that work performed by the SIP and SIPPING WG may be of 
   relevance.

   Pursuant to ITU-T Study Group 13 request for information on relevant and 
   related work in the IETF regarding emergency communications, we list 
   below RFCs and works in progress that we feel may be of interest to your 
   group.  Some of the completed work is Informational, and others are in 
   the category of Standards Track.

   Q.3/13 also requested that we keep you informed of any developments in 
   regards to emergency telecommunications. In those regards we would like 
   to make you aware that IETF mailing list participation and document 
   information is free and open for anyone. Allowing participants in Q.3/13 

"... free and open to anyone, allowing ..."

   to keep them selves informed of any developments. If Q.3/13 desire to 

"... themselves ..." (unless that's a US-ism)

   get further information about specific ongoing work, then please send a 
   liaison request to the responsible WG for those specific documents.

   The following list is divided under the associated working groups from 
   which the work has been done within the IETF.

Dale





From tsvwg-bounces@ietf.org Thu Aug 02 09:49:40 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGb3T-000771-GE; Thu, 02 Aug 2007 09:49:31 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IGb3S-00076p-5N
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 02 Aug 2007 09:49:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IGb3R-00076h-Qa
	for tsvwg@ietf.org; Thu, 02 Aug 2007 09:49:29 -0400
Received: from alnrmhc11.comcast.net ([206.18.177.51])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGb3R-0001r6-99
	for tsvwg@ietf.org; Thu, 02 Aug 2007 09:49:29 -0400
Received: from [192.168.1.2]
	(c-69-250-218-72.hsd1.md.comcast.net[69.250.218.72])
	by comcast.net (alnrmhc11) with SMTP
	id <20070802134928b1100r0ebre>; Thu, 2 Aug 2007 13:49:28 +0000
In-Reply-To: <1AC06006-FD5D-47B9-A839-B920241148FB@cisco.com>
References: <E1I400A-0005PX-DQ@stiedprstage1.ietf.org>
	<CB3E86CE-5A05-43B4-81AC-443B727F14D4@cisco.com>
	<6D1FB7A5-37E0-4708-A0F7-61B05251BFE4@g11.org.uk>
	<0879C74D-31CA-4F54-BC6D-1B8BC0F44B50@cisco.com>
	<1AC06006-FD5D-47B9-A839-B920241148FB@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B61B2664-AF7C-4051-8651-50858330F1E1@g11.org.uk>
Content-Transfer-Encoding: 7bit
From: ken carlberg <carlberg@g11.org.uk>
Subject: Re: [Tsvwg] draft-ietf-tsvwg-rsvp-proxy-proto-approaches
Date: Thu, 2 Aug 2007 09:49:25 -0400
To: Francois Le Faucheur IMAP <flefauch@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc: tsvwg tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Francois,

the new section you propose below looks fine by me.

cheers,

-ken


On Aug 1, 2007, at 6:01 AM, Francois Le Faucheur IMAP wrote:

> Hi Ken,
>
>>
>>>
>>> 5) Finally, this may be a nit, but it might be helpful to add a  
>>> Considerations section at the end of the document that mentions  
>>> the possible scenario of proxy reservations being established and  
>>> yet the end-host destination being unreachable/non-existent?   
>>> Proxy RSVP routers will know if the downstream leaf router is  
>>> reachable, but they won't necessarily know if the last hop to the  
>>> end host is reachable.  And since the proxy segment may be part  
>>> of an asymmetric path, one can't rely on upstream data to give a  
>>> hint to the proxy receiver that the destination is up.
>>>
>>> I don't think this is major liability, but just something that  
>>> needs to be mentioned to those that choose to deploy this work.
>>
>> I would say this consideration is not specific to the particular  
>> type of RSVP Proxy discussed in this document, but actually  
>> applicable to most RSVP Proxy scenario/approaches. So I would  
>> suggest we bring this point in the rsvp-proxy-approaches document.
>>
>> As you say, generally in practice I don't expect this is to be a  
>> major concern since application level-signaling would take place  
>> with the sender/receiver before RSVP reservations are established,  
>> so that if either is unreachable, application signaling will be  
>> affected first. But it is conceivable that receiver is reachable  
>> from application server and not reachable from sender. So we may  
>> as well bring up that point (in proxy-approaches).
>
> Below is the text I drafted to address your comment about un- 
> reachability scenarios. It is intended to go into a new section  
> (4.9). Let us know if you have any comments.
> Thanks
>
> Francois
>
>
> 4.9.  Reachability Considerations
>
>    There may be situations where the RSVP Receiver Proxy is  
> reachable by
>    the sender, while the receiver itself is not.  In such  
> situations, it
>    is possible that the RSVP Receiver Proxy is not always aware  
> that the
>    receiver is unreachable, and consequently may accept to  
> establish an
>    RSVP reservation on behalf of that receiver.  This would result in
>    unnecessary reservation establishment and unnecessary network
>    resource consumption.
>
>    This is not considered a significant practical concern for a number
>    of reasons.  First, in many cases, if the receiver is not reachable
>    from the sender, it will not be reachable either for application
>    signaling so that application level session establishment will  
> not be
>    possible in the first place.  Secondly, where the receiver is
>    unreachable from the sender but is reachable for application level
>    signaling (say because session establishment is performed  
> through an
>    off-path SIP agent that uses a different logical topology to
>    communicate with the receiver), then the sender may detect that the
>    receiver is unreachable before attempting reservation  
> establishment.
>    This may be achieved through mechanisms such as ICE's connectivity
>    check ( [I-D.ietf-mmusic-ice]).  Finally, even if the sender  
> does not
>    detect that the receiver is unreachable before triggering the RSVP
>    reservation establishment, it is very likely that the application
>    will quickly realise this lack of connectivity (e.g. the human
>    accepting the phone call on the receiver side will not hear the
>    human's voice on the sender side) and therefore tear down the  
> session
>    (e.g. hang up the phone) which in turn will trigger RSVP  
> reservation
>    release.
>
>    Nonetheless, it is recommended that network administrators consider
>    the above in light of their particular environment when deploying
>    RSVP Proxys.
>
>    The mirror considerations apply for situations involving an RSVP
>    Sender Proxy and where the sender cannot reach the destination  
> while
>    the RSVP Sender Proxy can.
>
>
>
>>
>> Thanks
>>
>> FRancois
>>
>>>
>>> -ken
>>>
>>>
>>
>
>






From tsvwg-bounces@ietf.org Fri Aug 03 08:04:08 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGvsw-0007L8-6x; Fri, 03 Aug 2007 08:04:02 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IGker-0003IJ-D0
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 02 Aug 2007 20:04:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGkem-0003E5-Tc; Thu, 02 Aug 2007 20:04:41 -0400
Received: from ihemail1.lucent.com ([135.245.0.33])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IGkem-0006jy-0T; Thu, 02 Aug 2007 20:04:40 -0400
Received: from ilexp03.ndc.lucent.com (h135-3-39-50.lucent.com [135.3.39.50])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l7304Ohr007049; 
	Thu, 2 Aug 2007 19:04:24 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp03.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Aug 2007 19:04:24 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.27]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Aug 2007 02:04:21 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] Re: [Tsvwg] Draft Liaision response to SG13
	onEmergency	Telecommunications
Date: Fri, 3 Aug 2007 02:04:20 +0200
Message-ID: <5D1A7985295922448D5550C94DE29180014EED0F@DEEXC1U01.de.lucent.com>
In-Reply-To: <OFF3619E59.61764BDC-ON8525732A.0058A6B2-8525732A.005997A1@csc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Re: [Tsvwg] Draft Liaision response to SG13
	onEmergency	Telecommunications
Thread-Index: AcfUV6mjGtO5TKErQSCBtjCYHVYrNAAx//qA
References: <46B0955A.3040900@ericsson.com>
	<OFF3619E59.61764BDC-ON8525732A.0058A6B2-8525732A.005997A1@csc.com>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Janet P Gunn" <jgunn6@csc.com>,
	"Magnus Westerlund" <magnus.westerlund@ericsson.com>
X-OriginalArrivalTime: 03 Aug 2007 00:04:21.0197 (UTC)
	FILETIME=[D7C5FFD0:01C7D561]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
X-Mailman-Approved-At: Fri, 03 Aug 2007 08:04:00 -0400
Cc: sip@ietf.org, IETF SIPPING WG <sipping@ietf.org>, tsvwg <tsvwg@ietf.org>,
	NSIS <nsis@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

While I wish to make no comment on the inclusion of other documents, I
would point out that the two drafts:
draft-polk-sip-rph-new-namespaces-01 and draft-ietf-sip-rph-response
were both discussed by the SIP WG and agreed that we would work on them.
This is still awaiting AD approval of the new milestones, but apart from
that, these are now essentially WG items. This does place them in a
different position to other author drafts.

Regards

Keith
________________________________

	From: Janet P Gunn [mailto:jgunn6@csc.com]=20
	Sent: Wednesday, August 01, 2007 5:19 PM
	To: Magnus Westerlund
	Cc: sip@ietf.org; IETF SIPPING WG; tsvwg; NSIS
	Subject: [Sip] Re: [Tsvwg] Draft Liaision response to SG13
onEmergency Telecommunications
=09
=09

=09
=09
=09
	Magnus Westerlund <magnus.westerlund@ericsson.com> wrote on
08/01/2007 10:14:50 AM:
=09
	> Janet P Gunn skrev:
	> >=20
	> > Magnus,
	> >=20
	> > You might want to add-
	> >=20
	> > draft-polk-tsvwg-signaled-domain-id-00.txt
	>=20
	> Well, I want to be somewhat restricted in adding individual
work into=20
	> the liaison. Also to me it is not clear how this is applicable
in the=20
	> emergency context.=20
=09
	Well, you included draft-polk-sip-rph-new-namespaces-01, and
draft-polk-tsvwg-signaled-domain-id-00 addresses the same scenarios.  It
would make sense to include either both or neither.
	>=20
	> > and
	> > draft-polk-ecrit-local-emergency-rph-namespace-01.txt
	> >
	>=20
	> Well, I got another comment about ECRIT WG document which we
hadn't=20
	> considered. I will contact the WG chairs and see what they
say.=20
=09
	Yes, ecrit should make the call. But I know at least one other
stds body (PacketCable PKT2 0-SP-RSTF-D01-060330 TCHG) is addressing it.

=09
	Janet
=09
	>=20
	> Cheers
	>=20
	> Magnus Westerlund
	>=20
	> IETF Transport Area Director & TSVWG Chair
	>
----------------------------------------------------------------------
	> Multimedia Technologies, Ericsson Research EAB/TVM/M
	>
----------------------------------------------------------------------
	> Ericsson AB                | Phone +46 8 4048287
	> Torshamsgatan 23           | Fax   +46 8 7575550
	> S-164 80 Stockholm, Sweden | mailto:
magnus.westerlund@ericsson.com
	>
----------------------------------------------------------------------
=09






From tsvwg-bounces@ietf.org Mon Aug 06 09:46:28 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1II2uY-0006W1-As; Mon, 06 Aug 2007 09:46:18 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1II2uW-0006Vw-LK
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 06 Aug 2007 09:46:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1II2uW-0006Vn-Bc
	for tsvwg@ietf.org; Mon, 06 Aug 2007 09:46:16 -0400
Received: from smtp2.smtp.bt.com ([217.32.164.150])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1II2uU-0006sI-Ld
	for tsvwg@ietf.org; Mon, 06 Aug 2007 09:46:16 -0400
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Aug 2007 14:46:12 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by
	i2kc06-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 6 Aug 2007 14:46:07 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
	cbibipnt05.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a
	P0803.399); id 1186407966158; Mon, 6 Aug 2007 14:46:06 +0100
Received: from mut.jungle.bt.co.uk ([10.215.130.87])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l76Dk3le002776; Mon, 6 Aug 2007 14:46:05 +0100
Message-Id: <5.2.1.1.2.20070806143443.02c53f20@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Mon, 06 Aug 2007 14:46:08 +0100
To: Sally Floyd <sallyfloyd@mac.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <db506707967feeedb704118ece0639c5@mac.com>
References: <5.2.1.1.2.20070731234936.04a65eb8@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070731234936.04a65eb8@pop3.jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 06 Aug 2007 13:46:07.0681 (UTC)
	FILETIME=[23F7A310:01C7D830]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Cc: tsvwg WG <tsvwg@ietf.org>
Subject: [Tsvwg] Re: feedback on draft-briscoe-tsvwg-ecn-tunnel-00
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Sally,

I've snipped the points of agreement; one remaining issue below but I think 
we are close to resolution...

At 23:16 01/08/2007, Sally Floyd wrote:
>Bob -
>
>>>Section 3.2:
>>>"It might be useful for the tunnel egress to be able to tell whether
>>>congestion occurred across a tunnel or upstream of it."
>>>
>>>The rest of the paragraph is specific to multi-level congestion
>>>marking such as PCN (and even in this case, I assume that the tunnel
>>>egress can only tell whether congestion occurred across the tunnel
>>>or upstream of it if the ECN field was not already at the highest
>>>of the multi levels at tunnel ingress).
>>>
>>>It seems *conceivable* to me that someone might want to design a
>>>tunnel where the egress would want to know whether congestion
>>>occurred across the tunnel or upstream of it, but where the ingress
>>>was not a Load Regulator.  (I don't know why, offhand, though
>>>multicast comes to mind.)  *If* one wanted to allow this in some
>>>future tunnel, then one should change the MUST about copying the
>>>ECN field from the inner to the outer header at ingress to a SHOULD.
>>>And if one didn't want to allow this, then this should be made as
>>>explicit as possible, I would say.  Making it completely clear that
>>>when the ECN field is copied from the inner to the outer header at
>>>ingress, then the tunnel egress won't necessarily be able to tell
>>>whether congestion occurred across a tunnel or upstream of it.
>>>(I guess that a simple way out would be just to stretch the
>>>definition of "Load Regulator", to say that any time the tunnel
>>>egress wants to be able to tell whether congestion occurred
>>>across the tunnel or upstream of it, the ingress is called a
>>>Load Regulator.)
>>
>>Actually, I think you'll find the rest of the para isn't specific to PCN 
>>and it answers your question (particularly from "But the same information 
>>could be gleaned...").
>
>As I read it, the rest of that paragraph is specific to
>multi-level congestion marking.

I just need to understand which words make you think this is about 
multi-level marking, because it wasn't meant to make the reader think like 
this. Here's the rest of the para. Can you indicate which part I should 
change to avoid implying multi-level.


"                                                           If outer
    header congestion marking was reset at the tunnel ingress ('I'), by
    the end of a tunnel ('E') the outer headers would indicate congestion
    experienced across the tunnel ('I' to 'E'), while the inner header
    would indicate congestion upstream of 'I'.  But the same information
    could be gleaned even if the tunnel ingress copied the inner to the
    outer headers.  By the end of the tunnel ('E'), any packet with an
    _extra_ mark in the outer header relative to the inner header would
    indicate congestion across the tunnel ('I' to 'E'), while the inner
    header would still indicate congestion upstream of ('I').
"

>>Essentially, even if the ingress copies the incoming header to the outer, 
>>any _additional_ marking along the tunnel can be detected at the tunnel 
>>egress as a difference between inner & outer.
>
>Yep.  But *additional* marking (for an ECN codepoint defined to
>have multi-level congestion, and for a packet that is not already
>marked at the highest level of congestion before the tunnel ingress)
>is one thing, and a packet that *would have been* marked in
>the tunnel if it hadn't already been marked is another.
>I think it is good to be quite clear about the difference.
>
>>Having realised this, there was no reason not to say MUST as:
>>- a single behaviour is always preferable to multiple options
>
>I happen to disagree.  The guideline that I use is not to specify
>"MUST" unless I think it is necessary.  I don't know off-hand if there
>is a specific IETF guideline on this.
>
>>- and copying at ingress actually doesn't lose info that might one day be 
>>useful about what happened across the tunnel.
>
>And I said above, I think this is wrong.  I think that copying at
>ingress is fine.  But I think it is good to be clear that is *does*
>lose information about routers that would have marked packets along
>the tunnel (e.g., for the default ECN semantics specified in RFC 3168,
>or for packets that were already marked at the highest level in a
>multi-level congestion mechanism).
>
>>Strictly, additional marking isn't quite the same as additional 
>>congestion (additional congestion which might have just happened to mark 
>>the same packet as was already marked). But, I don't think we should 
>>start introducing complicating options to allow for this corner case 
>>within some possible future scheme to extract what happened within the 
>>tunnel, that we're not sure anyone will ever want anyway. That corner 
>>case might be important to some scheme in the future during high 
>>congestion, but I suggest it will be their task to change MUST to SHOULD 
>>if they really need to.
>
>I would prefer "SHOULD", but I could live with "MUST".  But if the
>draft leaves it as MUST, then I think the draft should clarify that
>this means that the tunnel egress can't necessarily tell if a router
>in the tunnel would have marked the packet, because it is quite
>possible that the packet was already marked at the highest marking
>level before it entered the tunnel.

I v happy to say this.

>I would also suggest that
>the draft clarify that if someone in the future wanted to use
>a tunnel protocol where the egress router can detect whether packets
>are marked inside the tunnel, then they would have to change this
>"MUST" to a "SHOULD" or "MAY".

And I'm happy to say this. I'll put working in an -01 and post to the list.



Bob


____________________________________________________________________________
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







From tsvwg-bounces@ietf.org Tue Aug 07 07:40:08 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IINPv-000497-8Y; Tue, 07 Aug 2007 07:40:03 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IINPt-000490-Od
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 07 Aug 2007 07:40:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IINPt-00048j-Ev
	for tsvwg@ietf.org; Tue, 07 Aug 2007 07:40:01 -0400
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IINPr-0005A7-Qg
	for tsvwg@ietf.org; Tue, 07 Aug 2007 07:40:01 -0400
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Aug 2007 12:39:59 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by
	i2kc08-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 7 Aug 2007 12:39:58 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
	cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a
	P0803.399); id 1186486797396; Tue, 7 Aug 2007 12:39:57 +0100
Received: from mut.jungle.bt.co.uk ([10.215.130.87])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l77Bdr1J000757; Tue, 7 Aug 2007 12:39:57 +0100
Message-Id: <5.2.1.1.2.20070807115230.03d91d68@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Tue, 07 Aug 2007 12:39:58 +0100
To: "James M. Polk" <jmpolk@cisco.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Subject: Re: [Tsvwg] TSVWG *rough/draft* minutes
In-Reply-To: <XFE-SJC-212carcR4ZD00001fe0@xfe-sjc-212.amer.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 07 Aug 2007 11:39:58.0170 (UTC)
	FILETIME=[AE99ABA0:01C7D8E7]
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: tsvwg <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

James,

Look fairly accurate to me - thanks. Few gaps filled below:

1/ <draft-polk-tsvwg-signaled-domain-id-00.txt>
"*Bob wanted clarification of problem space, is a call a flow? And what
  happens when one subdomain contacts a node in another domain"
[After this pls add:]
- Are you interested in policy based on the location of the flow's sender, 
receiver or either/both?- Flows are between endpoints and they _cross_ 
network domains. It is always tricky to know if an endpoint is "in" 
(directly attached to) a remote domain.


2/ <draft-briscoe-tsvwg-byte-pkt-mark-00.txt>

"Sally - stated clearly this is not an update to RFC2309 (as ID says)."
[Pls remove "(as ID says)" and add:]
Bob: The ID doesn't say it updates 2309. That's just something I said in 
the presentation, which I'm happy to retract.

3/ <draft-floyd-tsvwg-besteffort-00.txt>
[Add: ]
Tim Shepard: What about where we go from here? What do you propose to do 
about heavy users?
Sally: Network operator is entitled to determine the balance of 
applications using its network

4/ <draft-briscoe-tsvarea-fair-02.pdf>
[Pls add after "very little time to give this preso"]
- not intending to replace existing regime, only adding
- we've got nothing to stop much more selfish apps evolving
- today fairness enforcement all outside IETF
- want to reveal an app-neutral metric (congestion) to operators for 
balancing network usage

[Also, at end, pls add:]
Bob: Lou Burness volunteered to edit (+co-authors from list) a forward 
looking informational I-D

Cheers


Bob
At 09:26 02/08/2007, James M. Polk wrote:
>TSVWG
>
>Here is the initial set of meeting minutes from IETF69 (Chicago)
>
>         http://www3.ietf.org/proceedings/07jul/minutes/tsvwg.txt
>
>I have not incorporated all the minutes sent to me yet, so the minutes 
>will change over the coming weeks. I wanted to get these out for early 
>review to help in their refinement.
>
>Comments are appreciated
>
>
>Cheers,
>James
>IETF TSVWG co-chair
>
>              ***********************************
>     "It should NEVER be inconvenient to do the right thing"

____________________________________________________________________________
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







From tsvwg-bounces@ietf.org Tue Aug 07 10:15:19 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IIPq5-0001it-SL; Tue, 07 Aug 2007 10:15:13 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IIPpw-0001hN-Bk
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 07 Aug 2007 10:15:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IIPpw-0001hF-0P; Tue, 07 Aug 2007 10:15:04 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IIPpv-0007aJ-Fq; Tue, 07 Aug 2007 10:15:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 2D8E0175D7;
	Tue,  7 Aug 2007 14:15:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IIPpu-0003xp-Lr; Tue, 07 Aug 2007 10:15:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IIPpu-0003xp-Lr@stiedprstage1.ietf.org>
Date: Tue, 07 Aug 2007 10:15:02 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: tsvwg@ietf.org
Subject: [Tsvwg] I-D ACTION:draft-ietf-tsvwg-diffserv-class-aggr-04.txt 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Transport Area Working Group Working Group of the IETF.

	Title		: Aggregation of DiffServ Service Classes
	Author(s)	: K. Chan, et al.
	Filename	: draft-ietf-tsvwg-diffserv-class-aggr-04.txt
	Pages		: 19
	Date		: 2007-8-7
	
In the core of a high capacity network, service differentiation may
   still be needed to support applications' utilization of the network.
   Applications with similar traffic characteristics and performance
   requirements are mapped into diffserv service classes based on end-
   to-end behavior requirements of the applications as indicated by
   Diffserv Service Classes [5].  However, some network segments may be
   configured in such a way that a single forwarding treatment may
   satisfy the traffic characteristics and performance requirements of
   two or more service classes.  In these cases, it may be desirable to
   aggregate two or more Diffserv Service Classes [5] into a single
   forwarding treatment.  This document provides guidelines for the
   aggregation of Diffserv Service Classes [5] into forwarding
   treatments.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-diffserv-class-aggr-04.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-tsvwg-diffserv-class-aggr-04.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-tsvwg-diffserv-class-aggr-04.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-8-7093539.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tsvwg-diffserv-class-aggr-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-tsvwg-diffserv-class-aggr-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-8-7093539.I-D@ietf.org>


--OtherAccess--

--NextPart--





From tsvwg-bounces@ietf.org Tue Aug 07 13:31:18 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IISth-0002FZ-NM; Tue, 07 Aug 2007 13:31:09 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IIStg-0002FQ-BS
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 07 Aug 2007 13:31:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IIStg-0002FI-1m
	for tsvwg@ietf.org; Tue, 07 Aug 2007 13:31:08 -0400
Received: from smtp4.smtp.bt.com ([217.32.164.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IIStd-0004nh-RQ
	for tsvwg@ietf.org; Tue, 07 Aug 2007 13:31:08 -0400
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Aug 2007 18:31:03 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by
	i2kc06-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 7 Aug 2007 18:31:02 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by
	cbibipnt05.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a
	P0803.399); id 1186507861861; Tue, 7 Aug 2007 18:31:01 +0100
Received: from mut.jungle.bt.co.uk ([10.215.130.87])
	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id
	l77HUjm6020273; Tue, 7 Aug 2007 18:31:00 +0100
Message-Id: <5.2.1.1.2.20070807155939.028437f8@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Tue, 07 Aug 2007 18:30:14 +0100
To: Joe Touch <touch@ISI.EDU>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Subject: Re: [Tsvwg] Does anyone have a defence in favour of flow rate 
	fairness?
In-Reply-To: <4681C537.6050101@isi.edu>
References: <5.2.1.1.2.20070626182056.04bd7c28@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070625203745.0498d6c0@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070615191706.0405ec80@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070615191706.0405ec80@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070625203745.0498d6c0@pop3.jungle.bt.co.uk>
	<5.2.1.1.2.20070626182056.04bd7c28@pop3.jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 07 Aug 2007 17:31:02.0882 (UTC)
	FILETIME=[BA25A420:01C7D918]
X-Spam-Score: 1.7 (+)
X-Scan-Signature: e274a7d5658fb8b0d6fbc93f042d014b
Cc: tsvwg IETF list <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Joe,

Sorry I left this thread dangling 5wks ago (with an offlist promise to get 
back to it). Four short family breaks and one IETF later you might still be 
interested...

Key to postings:
> >> >> Joe
> >> > Bob
> >> Joe
> > Bob
>  Joe
Bob

At 03:02 27/06/2007, Joe Touch wrote:
>Bob,
>
>These are all good arguments for IRTF study. See below.

The IETF/IRTF debate is currently fairly moot - Because the current 
'agreed' plan (following an informal ad hoc BoF in Prague, including the 
Transport ADs and the IRTF chair) was to continue building a community of 
interest around re-ECN in parallel to the IETF (thru mailing list below). 
Much the way HIP started. In parallel, the IETF only discusses fairness 
goals, not mechanism - yet. Then when/if the re-ECN community is ready, we 
can choose whether to ask to go IRTF or IETF.

Joining instructions for the re-ecn@ietf.org mailing list are here:
<https://www1.ietf.org/mailman/listinfo/re-ecn>
(not an official IETF w-g list)

Responses to all your other points follow...

>Bob Briscoe wrote:
> > Joe,
> >
> > At 05:58 26/06/2007, Joe Touch wrote:
> >
> >
> >> Bob Briscoe wrote:
> >> > Joe,
> >> >
> >> > just returned from a week off...
> >> ...
> >> >> "TCP's behavior defines a kind of fairness; staying inside the
> >> bounds of
> >> >> that fairness is what we currently defend, largely because it's
> >> deployed
> >> >> and appears to currently be reasonably sufficient"
> >> >>
> >> >> That does NOT mean we all consider TCP's behavior "flow rate fair",
> >> but
> >> >> rather that TCPs sharing a bottleneck will get some proportion of
> >> >> resources and both make progress, and that new CC mechanisms should
> >> not
> >> >> upend that 'balance' - whatever it currently is.
> >> >
> >> > Hmmm. TCPs each 'make progress' is rather clutching at straws, isn't
> >> it?
> >>
> >> It's a straw that is already firmly in our grasp. You're current
> >> proposal asks us to take a few things on faith:
> >>
> >> 1) that information about the remaining path is more important than
> >> information about the investment thus far
> >
> > I think there's a confusion here. The re-feedback protocol is designed
> > to reveal (D) downstream and (E) e2e path info to network elements, as
> > well as (U) upstream info already visible. They can then use whichever
> > is appropriate for different purposes...
>
>How do you reveal all that information in a single existing field? You
>only get one of upstream or downstream; either you start with a known or
>you end with a known. You can't have both.

It's in the re-ECN I-D
(apologies for the expiry when you tried to access - I fixed with an 
up-issue just before the Chicago IETF 
<http://www.ietf.org/internet-drafts/draft-briscoe-tsvwg-re-ecn-tcp-04.txt>)

I generally rely on colours to explain this. Consider ECN CE marking as 
colouring red. The sender has to colour as many bytes black as arrive red 
at the receiver, otherwise it risks packets being dropped. So each time the 
sender gets feedback of a red mark, it is worth colouring the next packet 
black. Black colouring remains unchanged e2e. Imagine on average there's 3% 
congestion by the end of a flow's path. With the above sender approach, 
looking at this flow anywhere along its length you will see a fraction of 
black bytes that is always 3% on average and a fraction of red bytes 
representing upstream congestion so far.

So in the diag below, if red U(pstream) = 2% of bytes and black E(2e) = 3%, 
you will know that D(ownstream) = E - U = 1%.

> >
> > <---------E-------------->
> > <--U--><------D---------->
> >

When I explained this at the ad hoc BoF in Prague (repeated in Chicago) I 
used a slide that allows you to grasp it quickly (Slide 10):
<http://www.cs.ucl.ac.uk/staff/B.Briscoe/present.html#0703re-ecn_arch>

[BTW, we're not using a "single existing field". Originally, we did manage 
to fit it within the ECN field (described in the original SIGCOMM paper), 
but my colleague worked out an attack on that one, so we had to resort to 
using the evil bit in the IP header. We just had a good ad hoc BoF session 
in Chicago trying to work round having to use the evil bit, to no avail so 
far.]

> > If a network wanted to police each flow's rate response to congestion
> > (which is possible but not necessary), it would use (E) e2e-path congestion
> >
> > If a network wanted to limit the bulk volume of congestion a user was
> > dumping into it, it would use (D) downstream congestion, simply to avoid
> > accounting for congestion that the user was causing in its own network.
> >
> > Neither need to be taken on faith:
> > (E) is what senders use for congestion response today, so the network
> > ingress seeing the same info a fraction of a RTT later allows it to
> > mirror the algo of the sender.
>
>Agreed.
>
> > (D) is the same as (E) at the ingress to a public internetwork if we
> > assume that congestion of the user's own local network is their concern.
>
>That would be a specific protocol for the ingress to public
>internetworks with that assumption. That would be one proposed protocol.

Strictly it would be a specific _use_ of a general protocol.


> > (D) allows a flat priced emulation of the congestion pricing that Kelly
> > proved optimises global utility under reasonable assumptions using tried
> > and tested methodology. Others have relaxed the assumptions and found
> > congestion volume is still the useful metric in all cases.
>
>That would be a case to be made to the IETF as a whole, to get everyone
>on board with your assumption of a goal for this work. I don't think it
>can be assumed, regardless of what has been studied to date.

Yes, I'm well aware that I have to push a rock up a hill, then another, 
then another. But more persuasion is not the same as more research.

Starting the persuasion game was the motivation for the I-D on flow-rate 
fairness vs. cost fairness. And that's why we're planning another more 
forward looking draft (with more skeptical co-authors) on why 
accountability for congestion is all the IETF needs to standardise.


> > Kelly showed that, once sources are accountable for the congestion they
> > cause they will want to prioritise (weight) their individual flows to
> > fit within the overall bulk envelope they choose. So we won't need
> > per-flow policing.
>
>The above statement appears to assume that per-source policing is in
>effect - i.e., that sources are accountable. That's still fairly
>fine-grained, isn't it?

When dealing with accountability, the graininess of the entities that are 
held to account have to match their autonomy.

This fine level of graininess would only be a problem if it had to be done 
remotely from the interface with the fine-grained entity. But we can do 
accountability and enforce it solely locally at the physical interface with 
the entity (trust boundary). And it's recursive, so an entity can be:
- a large ISP (at the interfaces with others at its border routers)
- or a large enterprise or campus (at the interfaces with its ISP/s)
- or a user within an enterprise/campus (interfacing with its site network)
- or a home network (at the interface with its access network ISP)
- or a mobile user (at the interface with its access network ISP)

In all cases accountability only requires a bulk measure of congestion 
volume (the diff between two bulk byte counters - equivalent complexity to 
subtracting two of the bulk byte counters displayed by netstat, once a month).

> > (D) also enables inter-domain accountability to propagate recursively,
> > by simple linear additivity.
> >
> > When we are talking about policing at the ingress to an internetwork,
> > the jump from (E) to (D) isn't a leap of faith, it's just saying let's
> > assume the user's machines all sit at her interface with her public
> > provider. She can 'unfairly' share her own resources as much as she wants.
>
>Right, but under current nets she can basically emulate as many "she"s
>as she wants; that's how we get HTTP opening multiple connections. Won't
>this just encourage multiple IP addresses to get around per-source policing?

No. It's not based on any identifiers. It's based on measurement of all 
traffic physically crossing the interface at a trust boundary.

If you're worried it will break if resources are virtualised, it won't. 
Some entity has to be responsible for the whole bundle of traffic crossing 
an interface (even if the entity is merely the group of users joint and 
severally responsible). Then that entity is responsible for dividing down 
the accountability within the bundle - further upstream where the entities 
separate (e.g. within the OS of a multi-user hosting server).

> > From then on the jump from policing single flows to only policing bulk
> > response to congestion is theory, but certainly not faith. And the
> > theory and its assumptions have been extended and checked ad infinitum
> > by other researchers over the past decade without particular cause for
> > concern. And we/others have built prototypes, built simulations etc.
> >
> > Anyway, you also have (E) to police individual flows if you don't
> > believe the theory-based jump to bulk policing. Spoilt for choice.
>
>(agreed that RTT is a red herring)
>
>...
> >> 2) that information about how resources are used along a path is useful
> >> in a multiparty congestion control system
> >>         vs., e.g., the fact that all component connections react
> >>         the same way, and that congestion relief occurs more rapidly
> >>         than congestion exploration
> >
> > "Info about how resources are used along a path" is exactly what
> > Internet senders use today to do multiparty congestion control
>
>Endpoints know what resources are available between those endpoints;
>that could include multipath. Nothing about today's (ubiquitous)
>congestion control is dependent on a particular path per se. The
>exception would be RSVP and/or XCP which touch routers on a path, but
>they're not exactly widespread (and that's part of the problem we're
>grappling with).

Because it's based on measuring congestion crossing a phys interface, not 
on identifiers, multipath just isn't any more of a problem than single path.


> > All the
> > proposal adds is making this info visible to the entity (the network)
> > that has the incentive to make sure the endpoints respond appropriately
> > to it.
>
>Why is it you think that endpoints aren't already responding
>appropriately to the information they get?

Two answers:
i) Streaming video is on the increase (when we - BT - originally started 
this work we predicted that on day 1 of switching all UK PSTN traffic to 
our new all-IP network, 40% of bytes would be unresponsive VoIP, but 
streamed video is becoming a greater concern now).
ii) TCP doesn't take account of flow duration or number of flows opened by 
one user - so I'm now challenging the community to justify why even using 
TCP as it stands is considered "responding appropriately" to congestion.


>How will this new system
>handle virtual paths and multipath?

See above - non-issue.

> > I'm not proposing we change anything about the dynamics of the
> > algorithms (relief/exploration). All that is necessary is to allow
> > different transfers between apps to behave as if they are w flows, where
> > w is a weight that may be <1 or >1.
>
>That seems nice in principle, but in practice what's to stop an app from
>faking being multiple apps to get more capacity? or multiple endpoints?
>Basically, what's to stop more 'gaming the system'?

Because accountability is not based on counting apps. It's based on how 
much congestion volume an economic entity has contracted to be allowed to 
cause - with its provider network. If it's a server farm, it needs to be 
able to create more congestion, so it contracts to do so. If it's an 
occasional user, she contracts for the minimum. If it's a heavy p2p user, 
she contracts for somewhere in between.

>I agree that the current system can be gamed - we don't really have
>per-connection (it's more like per-connection with RTT weighting, but
>not exactly), and we can open multiple connections to game it. However,
>replacing one game-able system with another doesn't solve that problem.

Pls come back if you manage to game re-ECN. The lastest incarnation has 
proved resistant so far (one spoofing DoS attack remains to be dealt with - 
see security considerations in the I-D).

My colleagues found holes in the original scheme, which we fixed making the 
scheme even simpler at the same time. Steve Bauer of MIT produced a paper 
with some plausible (and some implausible) strategies. Mark Handley also 
found a hole and my colleagues found some more. Since draft-02 all these 
strategies have been closed off ...

...except one of Steve Bauer's that I consider no system should have to 
defend against - the gamer uses perfect future knowledge of the sum of 
everyone else's future actions. If anyone had such knowledge, they could 
game the stock markets, flight-booking markets, goods markets - any market.

> > But, more freedom should be possible to allow experimentation (as with
> > the slower dynamics of TFRC).
>
>That is a ringing endorsement for an IRTF effort.

Well not exactly. Certainly IRTF effort would be nice on how to use the new 
freedom. But not necessarily blocking progress on the basic accountability 
mechanism.


> > However, if in the long distant future we find that everyone must "react
> > the same way" or more likely with some bound on their dynamics to keep
> > the network stable, ingress networks will have an incentive to enforce
> > that, and the necessary info and the control.
> >
> > So revealing info to the network provides evolutionary pressure towards
> > cost-fairness /and/ away from instability.
>
>That, IMO, would be a conclusion from an experiment we have not yet
>conducted. I'd like to see the result before coming to that conclusion.

Whether the network has the info to be able to take control is a fact of 
the proposed scheme, not a question. Certainly more research could be done 
to establish whether this control might be needed for stability in the 
future, but lack of such research results surely needn't hold up a 
mechanism for networks to bound the control of 'irresponsible' users, if it 
becomes necessary.


> >> 3) that your particular system is a good way to do either of the above
> >>
> >> Just asserting that "leave it alone" isn't good enough (which would
> >> likely have strong support), doesn't mean that this particular proposal
> >> is (or is not) a better way forward.
> >
> > I totally agree that I'm saying four things:
> > 1) flow rate fairness is pants (solid argument)
> > 2) cost-fairness is ultility-optimal in theory (solid argument)
> > 3) we have a reasonable implementation for cost fairness that wouldn't
> > require changes to ISP flat pricing (to be worked over by the community)
> > 4) once you have a cost-fairness mechanism, sub-communities can arrange
> > their own different fairness regimes between themselves (arm-wavy but
> > self-evident)
> >
> > If I had just blown apart flow rate fairness, without an alternative I
> > would (rightly) have been given a few cycles of people's attention then
> > ignored.
> >
> > Methinks you do expect too much.
>
>For the IETF, no. For the IRTF, yes. ;-)

As I said, moot at the mo.

Cheers


Bob


>Joe
>
>

____________________________________________________________________________
Bob Briscoe, <bob.briscoe@bt.com>      Networks Research Centre, BT Research
B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK.    +44 1473 645196 







From tsvwg-bounces@ietf.org Wed Aug 08 04:44:59 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IIh8J-0003P0-VC; Wed, 08 Aug 2007 04:43:11 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IIh8I-0003Oq-El
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 08 Aug 2007 04:43:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IIh8I-0003Oi-2P
	for tsvwg@ietf.org; Wed, 08 Aug 2007 04:43:10 -0400
Received: from elasmtp-galgo.atl.sa.earthlink.net ([209.86.89.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IIh8G-00024u-N0
	for tsvwg@ietf.org; Wed, 08 Aug 2007 04:43:10 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
	b=m4W4Lu/AyH5gAak01OHrCCqrKl1VByG0T1Hfj+hjh+KcqXKUqju6anT1965CzNhd;
	h=Received:Message-ID:Date:From:X-Sender:X-Mailer:X-Accept-Language:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [68.164.93.14] (helo=earthlink.net)
	by elasmtp-galgo.atl.sa.earthlink.net with asmtp (Exim 4.34)
	id 1IIh8G-0000ww-A2
	for tsvwg@ietf.org; Wed, 08 Aug 2007 04:43:08 -0400
Message-ID: <46B98225.DDBBFD56@earthlink.net>
Date: Wed, 08 Aug 2007 01:43:17 -0700
From: Erblichs <erblichs@earthlink.net>
X-Sender: "Erblichs" <erblichs@earthlink.net@smtpauth.earthlink.net>
	(Unverified)
X-Mailer: Mozilla 4.72 [en]C-gatewaynet  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: tsvwg@ietf.org
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 074f60c55517ea841aa676d7e74259b7b3291a7d08dfec7933b610622f7e01a4778343d95d175c3b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.164.93.14
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Subject: [Tsvwg] re: draft-floyd-tsvwg-besteffort-00b.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

0) Why isn't best-effort really more appropriate to IP than
   to TCP/UDP??? Routing is done via IP, and isn't best
   effort the attempt to route one or more pkts from
   a src to a dst????????

   ie, if a route doesn't exist from a src to a dst, then
   IMO, no effort of TCP or UDP or whatever is going to
   change the outcome..

======

1) some Nits first:

2.1 The Usefulness of Simple Best-Effort Traffic

weaknessas as well as many of the strengths of simple best-effort

-----> spelling : weaknessas > weaknesses

===============


the consensus goal for resourse allocation in the Internet, either in

------>spelling : resourse > resource

================
5.1.  From the IETF

policy issues concerning the approproate granularity of a "flow", and

------->spelling: approproate > appropriate



2) 2.2.1 QoS

Some users would be happy to pay for more bandwidth, less delay, less
   jitter, or fewer packet drops.  It is desirable to accommodate such
   goals in the Internet architecture while preserving a sufficient
   amount of bandwidth for best-effort traffic.


--->while preserving a sufficient
   amount of bandwidth for best-effort traffic.

WOULD this be more appropriate????

while allowing unused bandwidth to be used for best-effort traffic.

Are some applications inflexible to acceptance of any disturbance of
a somewhat constant bit rate flow? And decreasing packet drops, etc
within a application with a higher bit-cost may be an acceptable
alternative.


===============

3) 3.  On Flow-Rate Fairness for Simple Best-Effort Traffic
This section argues that rough flow-rate fairness is a perfectly
   acceptable goal for simple best-effort traffic.

Interesting....
Simple Best-Effort Traffic is defined in the 1.0 Introduction

"Simple best-effort
   traffic" in the current Internet uses end-to-end transport protocols
(e.g., TCP, UDP, or others)"

So how does "FAIRNESS" apply to a UDP and a TCP flow? Doesn't any
CC algorithm within TCP degrade performance versus a UDP flow?

Why aren't these two items discussed to accept a level of inequality
between UPD and TCP flows? Actually don't we accept a level of
"unfairness" even between two TCP flows at one point in time?

A simple case compares slow start versus congestion avoidance.
Are the doubling in flowrate per timeframe identifies a level
of unfairness or is the higher bitrate of a CA state flow?

4) 3.2.  The Limitations of Flow-Rate Fairness

??? Packets or bytes:

Does this include the effective throughput (total bytes - headers)
or the total number of bytes including the header bytes? 

Does the fairness go to the IP/TCP flow that has more bytes or more
packets? Both would mean fragmentation decreases fairness TOWARDS
the IP/TCP flow that is fragmenting. Right???

Unicast versus multicast : finally multicast.. Are any CC algors wrt
TCP really apply to multicast? IS it acceptable when one or more flows 
not reaching a dst from a src when MC is involved?





From tsvwg-bounces@ietf.org Wed Aug 08 23:01:29 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IIyFN-0003bZ-Pr; Wed, 08 Aug 2007 22:59:37 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IIyFM-0003TP-9X
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 08 Aug 2007 22:59:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IIyFL-0003R5-VH
	for tsvwg@ietf.org; Wed, 08 Aug 2007 22:59:35 -0400
Received: from smtpout.mac.com ([17.250.248.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IIyFK-0007vO-H1
	for tsvwg@ietf.org; Wed, 08 Aug 2007 22:59:35 -0400
Received: from mac.com (smtpin08-en2 [10.13.10.153])
	by smtpout.mac.com (Xserve/smtpout13/MantshX 4.0) with ESMTP id
	l792xVSr027393; Wed, 8 Aug 2007 19:59:31 -0700 (PDT)
Received: from [192.168.1.64] (adsl-70-231-228-113.dsl.snfc21.sbcglobal.net
	[70.231.228.113]) (authenticated bits=0)
	by mac.com (Xserve/smtpin08/MantshX 4.0) with ESMTP id l792xV7A004097; 
	Wed, 8 Aug 2007 19:59:31 -0700 (PDT)
In-Reply-To: <46B98225.DDBBFD56@earthlink.net>
References: <46B98225.DDBBFD56@earthlink.net>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <9c464cfdb8b2afec964f6f36937c84ac@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Subject: Re: [Tsvwg] re: draft-floyd-tsvwg-besteffort-00b.txt
Date: Wed, 8 Aug 2007 19:59:34 -0700
To: Erblichs <erblichs@earthlink.net>
X-Mailer: Apple Mail (2.624)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Cc: tsvwg WG <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

> 0) Why isn't best-effort really more appropriate to IP than
>    to TCP/UDP??? Routing is done via IP, and isn't best
>    effort the attempt to route one or more pkts from
>    a src to a dst????????
>
>    ie, if a route doesn't exist from a src to a dst, then
>    IMO, no effort of TCP or UDP or whatever is going to
>    change the outcome..

Yep, best-effort is about IP and about the transport protocol.

> ======
>
> 1) some Nits first:

Thanks.  The nits were fixed in draft-floyd-tsvwg-besteffort-00.txt
(June 2007).

> 2) 2.2.1 QoS
>
> Some users would be happy to pay for more bandwidth, less delay, less
>    jitter, or fewer packet drops.  It is desirable to accommodate such
>    goals in the Internet architecture while preserving a sufficient
>    amount of bandwidth for best-effort traffic.
>
>
> --->while preserving a sufficient
>    amount of bandwidth for best-effort traffic.
>
> WOULD this be more appropriate????
>
> while allowing unused bandwidth to be used for best-effort traffic.

I don't think so.  I personally don't think it would be a desirable
or appropriate goal to allow QoS-enabled traffic to use all of the
bandwidth, if so desired, with no unused bandwidth "left over" for
best-effort traffic.  And your rephrased sentence leaves open the
issue of whether the QoS traffic is managed to leave some "unused
bandwidth" for best-effort traffic.

> Are some applications inflexible to acceptance of any disturbance of
> a somewhat constant bit rate flow? And decreasing packet drops, etc
> within a application with a higher bit-cost may be an acceptable
> alternative.

Yep.  This document is not trying to specify how QoS-enabled or
higher-cost services might be delivered.

> ===============
>
> 3) 3.  On Flow-Rate Fairness for Simple Best-Effort Traffic
> This section argues that rough flow-rate fairness is a perfectly
>    acceptable goal for simple best-effort traffic.
>
> Interesting....
> Simple Best-Effort Traffic is defined in the 1.0 Introduction
>
> "Simple best-effort
>    traffic" in the current Internet uses end-to-end transport protocols
> (e.g., TCP, UDP, or others)"
>
> So how does "FAIRNESS" apply to a UDP and a TCP flow? Doesn't any
> CC algorithm within TCP degrade performance versus a UDP flow?

Good point.  I will add a discussion in Section 3.2 on "The Limitations
of Flow-Rate Fairness" about UDP.

> Why aren't these two items discussed to accept a level of inequality
> between UPD and TCP flows? Actually don't we accept a level of
> "unfairness" even between two TCP flows at one point in time?
>
> A simple case compares slow start versus congestion avoidance.
> Are the doubling in flowrate per timeframe identifies a level
> of unfairness or is the higher bitrate of a CA state flow?

Section 3.2 of draft-floyd-tsvwg-besteffort-00.txt makes
it pretty clear that we accept a level of unfairness between
two TCP flows.  But I will it as an explicit discussion point.

> 4) 3.2.  The Limitations of Flow-Rate Fairness
>
> ??? Packets or bytes:
>
> Does this include the effective throughput (total bytes - headers)
> or the total number of bytes including the header bytes?

I will add this as a question.  (This is explicitly addressed in
RFC 4828, on " TCP Friendly Rate Control (TFRC): The Small-Packet
(SP) Variant".)

> Does the fairness go to the IP/TCP flow that has more bytes or more
> packets? Both would mean fragmentation decreases fairness TOWARDS
> the IP/TCP flow that is fragmenting. Right???

I think this depends on the details of the transport protocol.
(Meaning that I don't know off-hand.)

> Unicast versus multicast : finally multicast.. Are any CC algors wrt
> TCP really apply to multicast? IS it acceptable when one or more flows
> not reaching a dst from a src when MC is involved?

Well, unicast vs. multicast is all open questions.  Fortunately, this
document doesn't try to answer any of them...

- Sally
http://www.icir.org/floyd/






From tsvwg-bounces@ietf.org Sat Aug 11 20:26:47 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IK1GO-0006Vy-AH; Sat, 11 Aug 2007 20:25:00 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IK1GM-0006Vc-U1
	for tsvwg-confirm+ok@megatron.ietf.org; Sat, 11 Aug 2007 20:24:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IK1GM-0006VT-KW; Sat, 11 Aug 2007 20:24:58 -0400
Received: from vapor.isi.edu ([128.9.64.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IK1GM-0003Lr-4r; Sat, 11 Aug 2007 20:24:58 -0400
Received: from [128.9.176.38] (c1-vpn8.isi.edu [128.9.176.38])
	by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id l7C0OcQV009619;
	Sat, 11 Aug 2007 17:24:38 -0700 (PDT)
Message-ID: <46BE533B.4020702@isi.edu>
Date: Sat, 11 Aug 2007 17:24:27 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
Subject: Re: [Tsvwg] Re: [tcpm]
	Revision	ofdraft-larsen-tsvwg-port-randomization
References: <0C53DCFB700D144284A584F54711EC5803B6C80C@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC5803B6C80C@xmb-sjc-21c.amer.cisco.com>
X-Enigmail-Version: 0.95.3
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig8CAEC7343217B814B857CAAF"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: tcpm@ietf.org, tsvwg WG <tsvwg@ietf.org>, DCCP mailing list <dccp@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>, TSV Dir <tsv-dir@ietf.org>,
	ext@cisco.com, Murari Sridharan <muraris@microsoft.com>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig8CAEC7343217B814B857CAAF
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Anantha Ramaiah (ananth) wrote:
> Lars had sent an email to retain focus on the port randomization and
> hence this is going to my last comment... Pl see inline..
> =20
>>
>> Anantha Ramaiah (ananth) wrote:
>>> Murari,
>> ...
>>> - or do it in piecemeal, first buy more TCP option space,=20
>> standardize=20
>>> any one of the proposals for extending the TCP option=20
>> space. Then have=20
>>> an extended port option like yu suggest below. Then think=20
>> about other=20
>>> TCP fields requiring extension.
>> The problem is that buying more option space is equivalent to=20
>> requiring a whole new TCP header - it has the same problems=20
>> with backward compatibility. Previous attempts explored this=20
>=20
> New TCP header =3D=3D "Mountain" , IMO this is equivalent to using SCTP=
 in
> some sense.
>=20
> TCP option space =3D=3D "Molehill" , this is a "minimal" change with "s=
ome"
> backward compat issues which can be addressed.

This was tried before and was shown to be a mountain of equivalent size
to a new TCP header. The problem is that the space is needed in the SYN,
and there's no backward-compatible way to change the options in the
first packet sent.

> If I take your above para seriously, then you are in a way implying tha=
t
> there is no new TCP options possible :-( or in other words users of TCP=

> would be rationed to use only a few options in the initial SYN exchange=
=2E

I didn't mean to imply that; I meant to state that explcitly.

Joe


--------------enig8CAEC7343217B814B857CAAF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGvlM7E5f5cImnZrsRApzjAJ9oE+JA9kXKbPWrrpqMLhwgWjnENwCfcVH1
fHoqvKLmBy4aaytGftOyI8k=
=TkFZ
-----END PGP SIGNATURE-----

--------------enig8CAEC7343217B814B857CAAF--





From tsvwg-bounces@ietf.org Tue Aug 14 18:38:58 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL50e-0003H9-82; Tue, 14 Aug 2007 18:37:08 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IL50c-0003Fc-O9
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 14 Aug 2007 18:37:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IL50c-0003FU-Ef
	for tsvwg@ietf.org; Tue, 14 Aug 2007 18:37:06 -0400
Received: from elasmtp-galgo.atl.sa.earthlink.net ([209.86.89.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IL50b-0007yh-4f
	for tsvwg@ietf.org; Tue, 14 Aug 2007 18:37:06 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
	b=Q8DXQRMm65OqsomE2t6STr3/WxRDSbT6TQ4xUWzMh2uyUj5x2+A/8dwq4RbRkgaz;
	h=Received:Message-ID:Date:From:X-Sender:X-Mailer:X-Accept-Language:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [68.164.86.1] (helo=earthlink.net)
	by elasmtp-galgo.atl.sa.earthlink.net with asmtp (Exim 4.34)
	id 1IL50Z-0007Xu-P8; Tue, 14 Aug 2007 18:37:04 -0400
Message-ID: <46C22CCF.B7360AC5@earthlink.net>
Date: Tue, 14 Aug 2007 15:29:35 -0700
From: Erblichs <erblichs@earthlink.net>
X-Sender: "Erblichs" <erblichs@earthlink.net@smtpauth.earthlink.net>
	(Unverified)
X-Mailer: Mozilla 4.72 [en]C-gatewaynet  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: tsvwg WG <tsvwg@ietf.org>, Sally Floyd <sallyfloyd@mac.com>,
	Mark Allman <mallman@icir.org>
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 074f60c55517ea841aa676d7e74259b7b3291a7d08dfec79bbfab3954d1a1983fa1a38c905d2f9ae350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.164.86.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: 
Subject: [Tsvwg] draft-ietf-tsvwg-cc-alt-04.txt : Suggestion : Safe
	Operating zone
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Group, Sally Floyd, and Mark Allman,

	It seems that most CC algor have one common item
	which may be toooo generic, but I am going to
	suggest it here anyways..

	So, an additional checklist
	item within section "3. Guidelines" could be,,,

	(X) Plateau treatment of congestion levels

	A congestion control algorithm needs to identify and operate
	within safe plateaus, where the goal is to attempt to maximize
	(ie: bandwidth) and/or minimze (ie:delay) one or more operating 
	contraints. 

	The generic TCP implimentation operates within two coarse 
	plateaus: slow-start and congestion avoidance. The
	first plateau is normally quickly reached by coarse
	steps, while the second adds finer granularity.

	All congestion control algorithm MUST accept whether it actively
	transitions within both plateaus or operates only within
	one plateau. Quickstart is one CC algorithm that targets
	the first plateau.

	Mitchell Erblich





From tsvwg-bounces@ietf.org Wed Aug 15 07:34:02 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILH6f-00062X-1p; Wed, 15 Aug 2007 07:32:09 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1ILH6d-00061D-G4
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 15 Aug 2007 07:32:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILH6d-0005xu-22
	for tsvwg@ietf.org; Wed, 15 Aug 2007 07:32:07 -0400
Received: from pork.icsi.berkeley.edu ([192.150.186.19])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILH6b-00028a-KE
	for tsvwg@ietf.org; Wed, 15 Aug 2007 07:32:07 -0400
Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net
	[69.222.35.58])
	by pork.ICSI.Berkeley.EDU (8.12.11.20060308/8.12.11) with ESMTP id
	l7FBW3d6000578; Wed, 15 Aug 2007 04:32:03 -0700
Received: from lawyers.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net
	[69.222.35.58]) by guns.icir.org (Postfix) with ESMTP id 3F756E18EF6;
	Wed, 15 Aug 2007 07:31:57 -0400 (EDT)
Received: from lawyers.icir.org (localhost [127.0.0.1])
	by lawyers.icir.org (Postfix) with ESMTP id 43E90285E1E;
	Wed, 15 Aug 2007 07:31:55 -0400 (EDT)
To: Erblichs <erblichs@earthlink.net>
From: Mark Allman <mallman@icir.org>
In-Reply-To: <46C22CCF.B7360AC5@earthlink.net> 
Organization: ICSI Center for Internet Research (ICIR)
Song-of-the-Day: Lift Me Up
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_bOundary";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 15 Aug 2007 07:31:55 -0400
Message-Id: <20070815113155.43E90285E1E@lawyers.icir.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: tsvwg WG <tsvwg@ietf.org>
Subject: [Tsvwg] Re: draft-ietf-tsvwg-cc-alt-04.txt : Suggestion : Safe
 Operating zone 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mallman@icir.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

--=_bOundary
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline


Mitchell-

Two things.

> 	(X) Plateau treatment of congestion levels

First, I read your proposed addition several times last night and this
morning and am not at all sure what you're trying to say.  It seems to
me that your text just says that there are going to be operating regions
for a congestion controller?  I don't quite understand how this is a
'guideline'.  What exactly would someone with an alternate congestion
controller do with this 'guideline'?  How would they address it?

Second, pragmatically this document is finished.  It has passed WGLC and
IESG review and is being processed by the RFC editor.  We could probably
stop the process if there was a show stopper, but this does not strike
me as even close to that.  I think at this point we're basically going
to have to live with the imperfections that remain in the document.  Of
course, if the WG wants to get itself in an uproar and agree with you
then we'd certainly do something.

allman




--=_bOundary
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGwuQrWyrrWs4yIs4RAvBFAJ9ufkZW//Qh6tIX0IzMJyFRizFtAQCeN35L
IBOTJ3LMFwGwmAmj9hpVfB0=
=ksJ2
-----END PGP SIGNATURE-----
--=_bOundary--





From tsvwg-bounces@ietf.org Wed Aug 15 13:09:16 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILML9-0008OS-RR; Wed, 15 Aug 2007 13:07:27 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1ILML8-0008ON-CA
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 15 Aug 2007 13:07:26 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILML8-0008OE-1R
	for tsvwg@ietf.org; Wed, 15 Aug 2007 13:07:26 -0400
Received: from elasmtp-scoter.atl.sa.earthlink.net ([209.86.89.67])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILML7-0001Io-GF
	for tsvwg@ietf.org; Wed, 15 Aug 2007 13:07:25 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
	b=ADqsRfSiR3tc5N4VGHreKaE2qehCimkZY6JzkEvA5IpP52vCeLnXcFQwbYXlhdGl;
	h=Received:Message-ID:Date:From:X-Sender:X-Mailer:X-Accept-Language:MIME-Version:To:CC:Subject:References:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [68.164.86.1] (helo=earthlink.net)
	by elasmtp-scoter.atl.sa.earthlink.net with asmtp (Exim 4.34)
	id 1ILML6-000870-IO; Wed, 15 Aug 2007 13:07:24 -0400
Message-ID: <46C33374.707AC83F@earthlink.net>
Date: Wed, 15 Aug 2007 10:10:12 -0700
From: Erblichs <erblichs@earthlink.net>
X-Sender: "Erblichs" <erblichs@earthlink.net@smtpauth.earthlink.net>
	(Unverified)
X-Mailer: Mozilla 4.72 [en]C-gatewaynet  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: mallman@icir.org
References: <20070815113155.43E90285E1E@lawyers.icir.org>
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 074f60c55517ea841aa676d7e74259b7b3291a7d08dfec79415fb79cd6fe89514b5c46632c78ebff350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.164.86.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: tsvwg WG <tsvwg@ietf.org>
Subject: [Tsvwg] Re: draft-ietf-tsvwg-cc-alt-04.txt : Suggestion : Safe
	Operatingzone
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Mark Allman, et al,

	First, I am glad that you read it. :^)

	With its Expiration date about 4 months
	from now, Dec, my assumption is that it was
	still "fermenting".

	After I read the document again, I didn't
	see how like CC are compared, because
	there were no characteristics for "likeness".

	Thus,,,

	It is a attempt to generalize and state that 
	ALL CC algorithms can be subdivided.

	The defacto-standard subdivision is at "threshold".

	Then LIKE CC algorithms could be compared to 
	a set of rules and against themselves.

	So, if we agree that QUICKSTART targets the first
	plateau (startup to threshold), any algorithm that 
	also targets targets the first plateau could be
	compared. One COULD then state a set of rules
	that targets that set of algorithms. And it would
	not make sense to compare any CA algor with
	QUICKSTART or generate one set of rules for both.

	Mitchell Erblich
	----------------
	

Mark Allman wrote:
> 
> Mitchell-
> 
> Two things.
> 
> >       (X) Plateau treatment of congestion levels
> 
> First, I read your proposed addition several times last night and this
> morning and am not at all sure what you're trying to say.  It seems to
> me that your text just says that there are going to be operating regions
> for a congestion controller?  I don't quite understand how this is a
> 'guideline'.  What exactly would someone with an alternate congestion
> controller do with this 'guideline'?  How would they address it?
> 
> Second, pragmatically this document is finished.  It has passed WGLC and
> IESG review and is being processed by the RFC editor.  We could probably
> stop the process if there was a show stopper, but this does not strike
> me as even close to that.  I think at this point we're basically going
> to have to live with the imperfections that remain in the document.  Of
> course, if the WG wants to get itself in an uproar and agree with you
> then we'd certainly do something.
> 
> allman
> 
>   ------------------------------------------------------------------------
>    Part 1.2Type: application/pgp-signature





From tsvwg-bounces@ietf.org Wed Aug 15 13:44:47 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILMtV-0001nA-Ex; Wed, 15 Aug 2007 13:42:57 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1ILMtU-0001n4-3E
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 15 Aug 2007 13:42:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILMtT-0001mw-PA
	for tsvwg@ietf.org; Wed, 15 Aug 2007 13:42:55 -0400
Received: from pork.icsi.berkeley.edu ([192.150.186.19])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILMtT-0002Hv-9D
	for tsvwg@ietf.org; Wed, 15 Aug 2007 13:42:55 -0400
Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net
	[69.222.35.58])
	by pork.ICSI.Berkeley.EDU (8.12.11.20060308/8.12.11) with ESMTP id
	l7FHgcLp014897; Wed, 15 Aug 2007 10:42:38 -0700
Received: from lawyers.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net
	[69.222.35.58]) by guns.icir.org (Postfix) with ESMTP id EBACEE206A8;
	Wed, 15 Aug 2007 13:42:32 -0400 (EDT)
Received: from lawyers.icir.org (localhost [127.0.0.1])
	by lawyers.icir.org (Postfix) with ESMTP id C91E8286618;
	Wed, 15 Aug 2007 13:30:57 -0400 (EDT)
To: Erblichs <erblichs@earthlink.net>
From: Mark Allman <mallman@icir.org>
In-Reply-To: <46C33374.707AC83F@earthlink.net> 
Organization: ICSI Center for Internet Research (ICIR)
Song-of-the-Day: Just the Way You Are
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_bOundary";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 15 Aug 2007 13:30:57 -0400
Message-Id: <20070815173057.C91E8286618@lawyers.icir.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: tsvwg WG <tsvwg@ietf.org>
Subject: [Tsvwg] Re: draft-ietf-tsvwg-cc-alt-04.txt : Suggestion : Safe
 Operatingzone 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mallman@icir.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

--=_bOundary
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline


> 	With its Expiration date about 4 months
> 	from now, Dec, my assumption is that it was
> 	still "fermenting".

The expiration date in the draft (all drafts) is simply 6 months from
submission and it does not have anything to do with the process of
moving documents forward.  If you want to know the status of a draft you
need to follow along on the mailing list to see when it is advanced and
also you can look in the draft tracker
(https://datatracker.ietf.org/idtracker/) 

> 	After I read the document again, I didn't
> 	see how like CC are compared, because
> 	there were no characteristics for "likeness".

Two things.

First, I do not think our document was about comparing "like" things.
The goal of the document is not about trying to pick the best
alternative to help some facet of TCP's congestion control algorithms.
The goal of the draft is to help guide the process of making sure that
before we publish an RFC on some specific candidate scheme some minimum
amount of investigation has taken place to illuminate the impact the
alternate mechanism will have.

Second, I think you are asking for a level of detail that we were not
attempting to get into.  There is a bit of comparison in the document,
as far as relating the proposed scheme with the standard scheme.  It is
not clear to me that it is useful to say much beyond what we said.  This
document is a set of **guidelines**, not a **checklist**.  There is a
difference, with (IMHO) the latter being either very hard or
impossible.  If you think the IETF needs to specify a tighter list of
things that need to be done then I would suggest that you write up a
draft and see if there is consensus on it.

allman




--=_bOundary
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGwzhRWyrrWs4yIs4RAtVhAJ9w9fKdcCU3zJ51yjSbxgFMvIfLdgCdGA3Y
ys8KYp2cI+PnsFwW/vXzqZI=
=xYKh
-----END PGP SIGNATURE-----
--=_bOundary--





From tsvwg-bounces@ietf.org Wed Aug 15 19:13:31 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILS1g-00006u-5P; Wed, 15 Aug 2007 19:11:44 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1ILS1b-00006Q-F5
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 15 Aug 2007 19:11:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILS1b-00006D-3s; Wed, 15 Aug 2007 19:11:39 -0400
Received: from bosco.isi.edu ([128.9.168.207])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILS1a-0005aU-1T; Wed, 15 Aug 2007 19:11:39 -0400
Received: by bosco.isi.edu (Postfix, from userid 70)
	id DA55DDFA22; Wed, 15 Aug 2007 16:10:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20070815231043.DA55DDFA22@bosco.isi.edu>
Date: Wed, 15 Aug 2007 16:10:43 -0700 (PDT)
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [Tsvwg] RFC 4923 on Quality of Service (QoS) Signaling in a Nested
	Virtual Private Network
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4923

        Title:      Quality of Service (QoS) Signaling 
                    in a Nested Virtual Private Network 
        Author:     F. Baker, P. Bose
        Status:     Informational
        Date:       August 2007
        Mailbox:    fred@cisco.com, 
                    pratik.bose@lmco.com
        Pages:      38
        Characters: 92632
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-vpn-signaled-preemption-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4923.txt

Some networks require communication between an interior and exterior
portion of a Virtual Private Network (VPN) or through a concatenation
of such networks resulting in a nested VPN, but have sensitivities
about what information is communicated across the boundary, especially
while providing quality of service to communications with different
precedence.  This note seeks to outline the issues and the nature of
the proposed solutions based on the framework for Integrated Services
operation over Diffserv networks as described in RFC 2998.  This memo provides information for the Internet community.

This document is a product of the Transport Area Working Group
Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community. 
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...







From tsvwg-bounces@ietf.org Thu Aug 16 10:36:33 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILgQw-0001l8-44; Thu, 16 Aug 2007 10:34:46 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1ILgQu-0001l3-EA
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 16 Aug 2007 10:34:44 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1ILgQu-0001kv-50
	for tsvwg@ietf.org; Thu, 16 Aug 2007 10:34:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILgPv-0001J6-Ju
	for tsvwg@ietf.org; Thu, 16 Aug 2007 10:33:43 -0400
Received: from web53403.mail.re2.yahoo.com ([206.190.37.50])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1ILgPu-0008KH-Cq
	for tsvwg@ietf.org; Thu, 16 Aug 2007 10:33:43 -0400
Received: (qmail 18128 invoked by uid 60001); 16 Aug 2007 14:33:41 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=YR1rAhBkRkwOr/HaH4zAZTta+T0OIQxvy2RaeXCrOgHdZxsmBFWwmOcfkdRHBFsm18KtXx6dz8i8jjCNyo50q4mLBlEmSJ1ufcn3adnaLBwDXA30Dbvkva1wuUvtIHviHhtyE6NnSF6VvKm6o1ZlTWlNv85c4gFm2nvMo2WscW8=;
X-YMail-OSG: vNpNJzoVM1mew_bj3bTTQe41_ksDF1DLATs3bDq.UG2HOD84miEVQkBnuYawKgmPAE_owFjff1YTrT.L1c97Itz5LhIfUfhxxABO3wK0guVBF63szv7Gi0gHF0YTl8K0HxYElFL8OIBVsMK.KQ5qyVEOyQ--
Received: from [212.117.81.29] by web53403.mail.re2.yahoo.com via HTTP;
	Thu, 16 Aug 2007 07:33:41 PDT
Date: Thu, 16 Aug 2007 07:33:41 -0700 (PDT)
From: kzu kzu <kzu_inatel@yahoo.com>
To: tsvwg@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-282993957-1187274821=:18062"
Content-Transfer-Encoding: 8bit
Message-ID: <840352.18062.qm@web53403.mail.re2.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
X-TMDA-Confirmed: Thu, 16 Aug 2007 10:34:44 -0400
Subject: [Tsvwg] Heartbeat information 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

--0-282993957-1187274821=:18062
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

hi,
   
  I have seen that the heartbeat information has Destination address, originator address and the time.
  However the chunck has quite a lot of zeros in it, like :
  Heartbeat information length with 56 bytes, where 
  1st 8 bytes are for Destination address: but first 4 bytes are filled out with zeros.
   
  Then there are 12 bytes with zero.
   
  After that the orignator address:
  8 bytes are for Destination address: but first 4 bytes are filled out with zeros.
   
  I was wondering where I can find a reference to the right implement heartbeat information.
   
  From 2960, 8.3 Path Heartbeat, I could only find the required data inside heartbeat information.
   
  Thank you in advance,
  /Kazuo

       
---------------------------------
Choose the right car based on your needs.  Check out Yahoo! Autos new Car Finder tool.
--0-282993957-1187274821=:18062
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div>hi,</div>  <div>&nbsp;</div>  <div>I have seen that the heartbeat information has Destination address, originator address and the time.</div>  <div>However the chunck has quite a lot of zeros in it, like :</div>  <div>Heartbeat information length with 56 bytes, where </div>  <div>1st 8 bytes are for Destination address: but first 4 bytes are filled out with zeros.</div>  <div>&nbsp;</div>  <div>Then there are 12 bytes with zero.</div>  <div>&nbsp;</div>  <div>After that the orignator address:</div>  <div>8 bytes are for Destination address: but first 4 bytes are filled out with zeros.</div>  <div>&nbsp;</div>  <div>I was wondering where I can find a reference to the&nbsp;right implement heartbeat information.</div>  <div>&nbsp;</div>  <div>From <FONT color=#0000ff><U>2960, </U></FONT><FONT color=#000000>8.3 Path Heartbeat, I could only find the required data inside heartbeat information.</FONT></div>  <div>&nbsp;</div>  <div>Thank you in advance,</div> 
 <div>/Kazuo</div><p>&#32;
      <hr size=1>Choose the right car based on your needs.  
Check out <a href="http://us.rd.yahoo.com/evt=48518/*http://autos.yahoo.com/carfinder/;_ylc=X3oDMTE3NWsyMDd2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDY2FyLWZpbmRlcg-- ">Yahoo! Autos new Car Finder tool.</a>

--0-282993957-1187274821=:18062--






From tsvwg-bounces@ietf.org Thu Aug 16 14:20:57 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILjw5-0000kz-6o; Thu, 16 Aug 2007 14:19:09 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1ILjw4-0000ku-7t
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 16 Aug 2007 14:19:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILjw3-0000km-Tl
	for tsvwg@ietf.org; Thu, 16 Aug 2007 14:19:07 -0400
Received: from gw.openss7.com ([142.179.199.224])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILjw3-0000ht-Du
	for tsvwg@ietf.org; Thu, 16 Aug 2007 14:19:07 -0400
Received: from ns.pigworks.openss7.net
	(IDENT:hW5OrItmZyTiorQWDOIv7HYVEkhiBW4I@ns1.evil.openss7.net
	[192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id l7GIJ6K23365;
	Thu, 16 Aug 2007 12:19:06 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id l7GIJ6C02732;
	Thu, 16 Aug 2007 12:19:06 -0600
Date: Thu, 16 Aug 2007 12:19:06 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: kzu kzu <kzu_inatel@yahoo.com>
Subject: Re: [Tsvwg] Heartbeat information
Message-ID: <20070816121906.A2683@openss7.org>
Mail-Followup-To: kzu kzu <kzu_inatel@yahoo.com>, tsvwg@ietf.org
References: <840352.18062.qm@web53403.mail.re2.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <840352.18062.qm@web53403.mail.re2.yahoo.com>;
	from kzu_inatel@yahoo.com on Thu, Aug 16, 2007 at 07:33:41AM -0700
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

kzu,

The format of the heartbeat information parameter is not specified
by the RFC and is up to the implementation.  Some implementations
pad the parameter out to a rather large size and use it for path
MTU discovery.  You have to decide what layout makes sense to your
implementation.  Also, be careful that some malicious endpoint might
manipulate the contents of the parameter.

--brian


kzu kzu wrote:                                (Thu, 16 Aug 2007 07:33:41)
> 
>    hi,
> 
> 
> 
>    I  have  seen  that the heartbeat information has Destination address,
>    originator address and the time.
> 
>    However the chunck has quite a lot of zeros in it, like :
> 
>    Heartbeat information length with 56 bytes, where
> 
>    1st  8 bytes are for Destination address: but first 4 bytes are filled
>    out with zeros.
> 
> 
> 
>    Then there are 12 bytes with zero.
> 
> 
> 
>    After that the orignator address:
> 
>    8  bytes are for Destination address: but first 4 bytes are filled out
>    with zeros.
> 
> 
> 
>    I  was  wondering  where I can find a reference to the right implement
>    heartbeat information.
> 
> 
> 
>    From  2960,  8.3  Path  Heartbeat, I could only find the required data
>    inside heartbeat information.
> 
> 
> 
>    Thank you in advance,
> 
>    /Kazuo
>      _________________________________________________________________
> 
>    Choose  the  right  car based on your needs. Check out [1]Yahoo! Autos
>    new Car Finder tool.
> 
> References
> 
>    1. http://us.rd.yahoo.com/evt=48518/*http://autos.yahoo.com/carfinder/;_ylc=X3oDMTE3NWsyMDd2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDY2FyLWZpbmRlcg--

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/





From tsvwg-bounces@ietf.org Mon Aug 20 03:00:24 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IN1Dc-0006zW-Co; Mon, 20 Aug 2007 02:58:32 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IH3Mv-0000nw-Rm
	for tsvwg-confirm+ok@megatron.ietf.org; Fri, 03 Aug 2007 16:03:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IH3Mv-0000no-IK
	for tsvwg@ietf.org; Fri, 03 Aug 2007 16:03:29 -0400
Received: from an-out-0708.google.com ([209.85.132.248])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IH3Mt-0000l3-Es
	for tsvwg@ietf.org; Fri, 03 Aug 2007 16:03:29 -0400
Received: by an-out-0708.google.com with SMTP id c17so177344anc
	for <tsvwg@ietf.org>; Fri, 03 Aug 2007 13:03:27 -0700 (PDT)
Received: by 10.100.119.14 with SMTP id r14mr1573348anc.1186122474522;
	Thu, 02 Aug 2007 23:27:54 -0700 (PDT)
Received: by 10.100.131.5 with HTTP; Thu, 2 Aug 2007 23:27:54 -0700 (PDT)
Message-ID: <d9eefe750708022327w77b237e6k59aaacbe6c7d4ddc@mail.gmail.com>
Date: Fri, 3 Aug 2007 11:57:54 +0530
From: "Mohammad Arif" <mohammad.arifb@gmail.com>
To: tsvwg@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_132901_6540637.1186122474494"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
X-Mailman-Approved-At: Mon, 20 Aug 2007 02:58:30 -0400
Subject: [Tsvwg] doubt in receving SCTP notifications using linux 2.6 kernel
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

------=_Part_132901_6540637.1186122474494
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi ,
I m using linux 2.6 kernel for our SCTP transport requirement.

*i have enabled all the events/notifications for an socket using setsockopt(
) sys call*
  events.sctp_data_io_event = 1;
  events.sctp_association_event = 1;
  events.sctp_send_failure_event = 1;
  events.sctp_shutdown_event = 1;
  events.sctp_peer_error_event = 1;

*And my notification receiving code is*

union sctp_notification *unSCTPNot;
char *pacbuffer;
int iFlags ;
struct sockaddr_in stSrcIPAddress;
socklen_t  Addlen;

iRet= sctp_recvmsg( iAssocID, (void *)pacbuffer,256 ,
                        (struct sockaddr *)&stSrcIPAddress, &Addlen,
&sndrcvinfo, &iFlags );

 if(iFlags & MSG_NOTIFICATION )
 {
      memcpy(&unSCTPNot,pacbuffer,iRet);
      //process the notifications
 }

Is the above procedure correct? please guide me.
because i dont have one more linux server to test the code right now..

Any help would be appreciated.

Thanks
-- 
Regards
Mohammad Arif


-- 
Regards
Mohammad Arif

------=_Part_132901_6540637.1186122474494
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<p>Hi ,<br>I m using linux 2.6 kernel for our SCTP transport requirement.</p>
<p><strong>i have enabled all the events/notifications for an socket using setsockopt( ) sys call</strong><br>&nbsp; events.sctp_data_io_event = 1;<br>&nbsp; events.sctp_association_event = 1;<br>&nbsp; events.sctp_send_failure_event = 1;
<br>&nbsp; events.sctp_shutdown_event = 1;<br>&nbsp; events.sctp_peer_error_event = 1;</p>
<p><strong>And my notification receiving code is</strong></p>
<p>union sctp_notification *unSCTPNot;<br>char *pacbuffer;<br>int iFlags ;<br>struct sockaddr_in stSrcIPAddress;<br>socklen_t&nbsp; Addlen;</p>
<p>iRet= sctp_recvmsg( iAssocID, (void *)pacbuffer,256 ,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (struct sockaddr *)&amp;stSrcIPAddress, &amp;Addlen, &amp;sndrcvinfo, &amp;iFlags );<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp;if(iFlags &amp; MSG_NOTIFICATION )
<br>&nbsp;{<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; memcpy(&amp;unSCTPNot,pacbuffer,iRet);<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; //process the notifications<br>&nbsp;}</p>
<p>Is the above procedure correct? please guide me.<br>because i dont have one more linux server to test the code right now..</p>
<p>Any help would be appreciated.</p>
<p>Thanks <br>-- <br>Regards<br>Mohammad Arif </p><br clear="all"><br>-- <br>Regards<br>Mohammad Arif 

------=_Part_132901_6540637.1186122474494--





From tsvwg-bounces@ietf.org Mon Aug 20 06:58:24 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IN4w1-0001Fc-UI; Mon, 20 Aug 2007 06:56:37 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IN4w0-0001FX-UZ
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 20 Aug 2007 06:56:36 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IN4w0-0001FP-KH
	for tsvwg@ietf.org; Mon, 20 Aug 2007 06:56:36 -0400
Received: from bgerelbas01.asiapac.hp.net ([15.219.201.134])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IN4w0-0003d2-2M
	for tsvwg@ietf.org; Mon, 20 Aug 2007 06:56:36 -0400
Received: from bgeexg12.asiapacific.cpqcorp.net
	(bgeexg12.asiapacific.cpqcorp.net [16.150.33.53])
	by bgerelbas01.asiapac.hp.net (Postfix) with ESMTP id E3F47330E1
	for <tsvwg@ietf.org>; Mon, 20 Aug 2007 16:27:06 +0530 (IST)
Received: from BGEEXC07.asiapacific.cpqcorp.net ([16.150.33.19]) by
	bgeexg12.asiapacific.cpqcorp.net with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 20 Aug 2007 16:26:33 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 20 Aug 2007 16:26:32 +0530
Message-ID: <7A54FE62F2476747893C388DE70DC0D9037D489C@BGEEXC07.asiapacific.cpqcorp.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Need info about connect behavior at SCTP when backlog limit is
	reached
Thread-Index: AcfjGMUlWfCrOkOCSvKh1sxqGNF7Gw==
From: "Ramaiah, Chaitra M (STSD)" <chaitra.m.ramaiah@hp.com>
To: <tsvwg@ietf.org>
X-OriginalArrivalTime: 20 Aug 2007 10:56:33.0834 (UTC)
	FILETIME=[C5AA48A0:01C7E318]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: [Tsvwg] Need info about connect behavior at SCTP when backlog limit
	is reached
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi All,

  I have a question regarding how connect should behave for SCTP sockets
when the listen backlog is reached. To elaborate, the server opens a 1-1
SCTP socket, binds and listens with a backlog of 1 and does not do an
accept. The client opens two sockets and connects to the server for the
two sockets. The first connect should go through fine as there is room
for one connection indication. What should happen when we issue the
second connect? For TCP the second connect will just timeout and connect
will return ETIMEDOUT after 75 seconds. What should be the behavior for
SCTP? Should it be on par with TCP and just ignore the request or should
it reply back with ABORT for the INIT? Thanks in advance for your reply.

Regards,
Chaitra






From tsvwg-bounces@ietf.org Mon Aug 20 08:09:56 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IN63F-0002ws-84; Mon, 20 Aug 2007 08:08:09 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IN63D-0002wn-J7
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 20 Aug 2007 08:08:07 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IN63D-0002wf-90
	for tsvwg@ietf.org; Mon, 20 Aug 2007 08:08:07 -0400
Received: from gw.openss7.com ([142.179.199.224])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IN63C-0005GB-PL
	for tsvwg@ietf.org; Mon, 20 Aug 2007 08:08:07 -0400
Received: from ns.pigworks.openss7.net
	(IDENT:DNDlWY7DOzSNABUDr5ouncZ6fEhvVOZ3@ns1.evil.openss7.net
	[192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id l7KC83K24207;
	Mon, 20 Aug 2007 06:08:03 -0600
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id l7KC83v26673;
	Mon, 20 Aug 2007 06:08:03 -0600
Date: Mon, 20 Aug 2007 06:08:03 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Ramaiah, Chaitra M (STSD)" <chaitra.m.ramaiah@hp.com>
Subject: Re: [Tsvwg] Need info about connect behavior at SCTP when backlog
	limit is reached
Message-ID: <20070820060803.B26493@openss7.org>
Mail-Followup-To: "Ramaiah, Chaitra M (STSD)" <chaitra.m.ramaiah@hp.com>,
	tsvwg@ietf.org
References: <7A54FE62F2476747893C388DE70DC0D9037D489C@BGEEXC07.asiapacific.cpqcorp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <7A54FE62F2476747893C388DE70DC0D9037D489C@BGEEXC07.asiapacific.cpqcorp.net>;
	from chaitra.m.ramaiah@hp.com on Mon, Aug 20, 2007 at 04:26:32PM +0530
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Ramaiah,,

For TCP it is in fact implementation dependent, as it should be for SCTP.

--brian

Ramaiah, Chaitra M (STSD) wrote:                (Mon, 20 Aug 2007 16:26:32)
> Hi All,
> 
>   I have a question regarding how connect should behave for SCTP sockets
> when the listen backlog is reached. To elaborate, the server opens a 1-1
> SCTP socket, binds and listens with a backlog of 1 and does not do an
> accept. The client opens two sockets and connects to the server for the
> two sockets. The first connect should go through fine as there is room
> for one connection indication. What should happen when we issue the
> second connect? For TCP the second connect will just timeout and connect
> will return ETIMEDOUT after 75 seconds. What should be the behavior for
> SCTP? Should it be on par with TCP and just ignore the request or should
> it reply back with ABORT for the INIT? Thanks in advance for your reply.
> 
> Regards,
> Chaitra
> 
> 

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/





From tsvwg-bounces@ietf.org Mon Aug 20 11:55:26 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IN9ZU-0001PN-6E; Mon, 20 Aug 2007 11:53:40 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IN9ZS-0001PI-GV
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 20 Aug 2007 11:53:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IN9ZS-0001P5-6W
	for tsvwg@ietf.org; Mon, 20 Aug 2007 11:53:38 -0400
Received: from drew.ipv6.franken.de ([2001:638:a02:a001:20e:cff:fe4a:feaa]
	helo=mail-n.franken.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IN9ZQ-0000MN-Ua
	for tsvwg@ietf.org; Mon, 20 Aug 2007 11:53:38 -0400
Received: from [172.31.0.228] (p2067-ipbf212kyoto.kyoto.ocn.ne.jp
	[222.148.191.67])
	by mail-n.franken.de (Postfix) with ESMTP id D47E2801AC25;
	Mon, 20 Aug 2007 17:53:16 +0200 (CEST)
	(KNF-authenticated sender: macmic)
In-Reply-To: <7A54FE62F2476747893C388DE70DC0D9037D489C@BGEEXC07.asiapacific.cpqcorp.net>
References: <7A54FE62F2476747893C388DE70DC0D9037D489C@BGEEXC07.asiapacific.cpqcorp.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C0D2529D-01D3-4E55-8C49-F53A1406B33F@lurchi.franken.de>
Content-Transfer-Encoding: 7bit
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: [Tsvwg] Need info about connect behavior at SCTP when backlog
	limit is reached
Date: Mon, 20 Aug 2007 17:47:50 +0200
To: "Ramaiah, Chaitra M (STSD)" <chaitra.m.ramaiah@hp.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi Chaitra,

when receiving a COOKIE-ECHO you can either send back an ABORT
to indicate that you are out of resources or you can hope that
this is only a temporary issue and just drop the COOKIE-ECHO in
the hope that when the retransmission of the COOKIE-ECHO arrives
the situation has changed.

In response to the INIT chunk I would always return an INIT-ACK.

There is no need to run a timer on the server side.

Best regards
Michael


On Aug 20, 2007, at 12:56 PM, Ramaiah, Chaitra M (STSD) wrote:

> Hi All,
>
>   I have a question regarding how connect should behave for SCTP  
> sockets
> when the listen backlog is reached. To elaborate, the server opens  
> a 1-1
> SCTP socket, binds and listens with a backlog of 1 and does not do an
> accept. The client opens two sockets and connects to the server for  
> the
> two sockets. The first connect should go through fine as there is room
> for one connection indication. What should happen when we issue the
> second connect? For TCP the second connect will just timeout and  
> connect
> will return ETIMEDOUT after 75 seconds. What should be the behavior  
> for
> SCTP? Should it be on par with TCP and just ignore the request or  
> should
> it reply back with ABORT for the INIT? Thanks in advance for your  
> reply.
>
> Regards,
> Chaitra
>
>
>
>






From tsvwg-bounces@ietf.org Wed Aug 22 20:25:45 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IO0UN-0003EV-1W; Wed, 22 Aug 2007 20:23:55 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IO0UH-0003Bu-Ca
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 22 Aug 2007 20:23:49 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IO0UH-0003Bi-1g; Wed, 22 Aug 2007 20:23:49 -0400
Received: from bosco.isi.edu ([128.9.168.207])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IO0UG-0006YQ-IH; Wed, 22 Aug 2007 20:23:48 -0400
Received: by bosco.isi.edu (Postfix, from userid 70)
	id 24391DFF54; Wed, 22 Aug 2007 17:22:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20070823002223.24391DFF54@bosco.isi.edu>
Date: Wed, 22 Aug 2007 17:22:23 -0700 (PDT)
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [Tsvwg] BCP 133,
	RFC 5033 on Specifying New Congestion Control Algorithms
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


A new Request for Comments is now available in online RFC libraries.

        BCP 133        
        RFC 5033

        Title:      Specifying New Congestion Control Algorithms 
        Author:     S. Floyd, M. Allman
        Status:     Best Current Practice
        Date:       August 2007
        Mailbox:    floyd@icir.org, 
                    mallman@icir.org
        Pages:      10
        Characters: 23469
        Updates:    
        See-Also:   BCP0133

        I-D Tag:    draft-ietf-tsvwg-cc-alt-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5033.txt

The IETF's standard congestion control schemes have been widely
shown to be inadequate for various environments (e.g., high-speed
networks).  Recent research has yielded many alternate congestion
control schemes that significantly differ from the IETF's congestion
control principles.  Using these new congestion control schemes in
the global Internet has possible ramifications to both the traffic
using the new congestion control and to traffic using the currently
standardized congestion control.  Therefore, the IETF must proceed
with caution when dealing with alternate congestion control
proposals.  The goal of this document is to provide guidance for
considering alternate congestion control algorithms within the IETF.  
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.

This document is a product of the Transport Area Working Group
Working Group of the IETF.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...







From tsvwg-bounces@ietf.org Thu Aug 23 10:33:54 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IODjE-0001n8-By; Thu, 23 Aug 2007 10:32:08 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IODjD-0001n0-FU
	for tsvwg-confirm+ok@megatron.ietf.org; Thu, 23 Aug 2007 10:32:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IODjD-0001ms-5t; Thu, 23 Aug 2007 10:32:07 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IODjB-0007S0-G9; Thu, 23 Aug 2007 10:32:07 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l7NEVPh7022008; Thu, 23 Aug 2007 17:32:01 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Aug 2007 17:31:31 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Aug 2007 17:31:31 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh102.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 23 Aug 2007 17:31:31 +0300
Received: from [172.21.37.28] (esdhcp03728.research.nokia.com [172.21.37.28])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l7NEVUTr025697; Thu, 23 Aug 2007 17:31:30 +0300
In-Reply-To: <96AB315B-327A-49AF-83CA-A4012F6A5153@csperkins.org>
References: <E1I7psX-0004oc-Bu@stiedprstage1.ietf.org>
	<96AB315B-327A-49AF-83CA-A4012F6A5153@csperkins.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-62--881124343;
	protocol="application/pkcs7-signature"
Message-Id: <4FA00E40-69A3-4B92-A5DA-04E83054D771@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
Subject: Re: [Tsvwg] I-D Action:draft-ietf-tsvwg-udp-guidelines-02.txt 
Date: Thu, 23 Aug 2007 17:31:12 +0300
To: ext Colin Perkins <csp@csperkins.org>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 23 Aug 2007 14:31:31.0556 (UTC)
	FILETIME=[4C8BBA40:01C7E592]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Cc: Godred Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg WG <tsvwg@ietf.org>,
	MMUSIC WG <mmusic@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


--Apple-Mail-62--881124343
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

On 2007-7-23, at 19:20, ext Colin Perkins wrote:
> On 9 Jul 2007, at 04:50, Internet-Drafts@ietf.org wrote:
>> http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-udp- 
>> guidelines-02.txt
>
> Section 3.5 states:
>
>    Applications MAY in addition send periodic keep-alive messages to
>    attempt to refresh middlebox state.  Unfortunately, no common  
> timeout
>    has been specified for per-flow UDP state for arbitrary  
> middleboxes.
>    For NATs, [RFC4787] requires a state timeout of 2 minutes or  
> longer,
>    and it is likely that other types of middleboxes use timeouts of
>    similar timescales.  Consequently, if applications choose to send
>    periodic keep-alives, they SHOULD NOT send them more frequently  
> than
>    once every two minutes.  (Not that some deployed middleboxes use a
>    shorter timeout value than 2 minutes, violating [RFC4787].)
>
> which is fine, except that draft-ietf-mmusic-ice-17 suggests a 15  
> second keep alive interval by default. Can we align these?

We discussed this in the hallways in Chicago, and I've become  
grudgingly convinced that for specialized uses of UDP, where  
communication disruptions due to disappearing middlebox state are  
highly problematic (e.g., media transmission), 15-second timeouts are  
probably needed. But I did want to make it clear that such timeouts -  
or even the use of keepalives in general - are not recommended for  
arbitrary UDP applications.

Below is the modified Section 3.5 from my working copy of -03 FYI.  
Please let me know what you think of the changes.

Lars


3.5.  Middlebox Traversal Guidelines

    Network address translators (NATs) and firewalls are examples of
    intermediary devices ("middleboxes") that can exist along an end-to-
    end path.  A middlebox typically performs a function that  
requires it
    to maintain per-flow state.  For connection-oriented protocols, such
    as TCP, middleboxes snoop and parse the connection-management  
traffic
    and create and destroy per-flow state accordingly.  For a
    connectionless protocol such as UDP, this approach is not possible.
    Consequently, middleboxes may create per-flow state when they see a
    packet that indicates a new flow, and destroy the state after some
    period of time during which no packets belonging to the same flow
    have arrived.

    Depending on the specific function that the middlebox performs, this
    behavior can introduce a time-dependency that restricts the kinds of
    UDP traffic exchanges that will be successful across the middlebox.
    For example, NATs and firewalls typically define the partial path on
    one side of them to be interior to the domain they serve, whereas  
the
    partial path on their other side is defined to be exterior to that
    domain.  Per-flow state is typically created when the first packet
    crosses from the interior to the exterior, and while the state is
    present, NATs and firewalls will forward return traffic.  Return
    traffic arriving after the per-flow state has timed out is dropped,
    as is other traffic arriving from the exterior.

    Many applications that use UDP for communication operate across
    middleboxes without needing to employ additional mechanisms.  One
    example is the DNS, which has a strict request-response  
communication
    pattern that typically completes within seconds.

    Other applications may experience communication failures when
    middleboxes destroy the per-flow state associated with an  
application
    session during periods when the application does not exchange any  
UDP
    traffic.  Applications SHOULD be able to gracefully handle such
    communication failures and implement mechanisms to re-establish  
their
    UDP sessions.

    For some applications, such as media transmissions, this re-
    synchronization is highly undesirable, because it can cause user-
    perceivable playback artifacts.  Such specialized applications MAY
    send periodic keep-alive messages to attempt to refresh middlebox
    state.  It is important to note that keep-alive messages are NOT
    RECOMMENDED for general use - they are unnecessary for many
    applications and can consume significant amounts of system and
    network resources.

    An application that needs to employ keep-alives to deliver useful
    service in the presence of middleboxes SHOULD NOT transmit them more
    frequently than once every 15 seconds and SHOULD strongly consider
    using longer intervals.  No common timeout has been specified for
    per-flow UDP state for arbitrary middleboxes.  For NATs, [RFC4787]
    requires a state timeout of 2 minutes or longer.  However, empirical
    evidence suggests that a significant fraction of the deployed
    middleboxes unfortunately uses shorter timeouts.  The timeout of 15
    seconds originates with the Interactive Connectivity Establishment
    (ICE) protocol [I-D.ietf-mmusic-ice].

    It is important to note that sending keep-alives is not a substitute
    for implementing a robust connection handling.  Like all UDP
    messages, keep-alives can be delayed or dropped, causing middlebox
    state to time out.  In addition, the congestion control  
guidelines in
    Section 3.1 cover all UDP transmissions by an application, including
    the transmission of middlebox keep-alives.  Congestion control may
    thus lead to delays or temporary suspension of keep-alive
    transmission.


--Apple-Mail-62--881124343
Content-Transfer-Encoding: base64
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGQDCCAvkw
ggJioAMCAQICEGtxkLFHQu1g67hlmYfwPuIwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA3MDEwNDE2MTE1NFoXDTA4MDEwNDE2MTE1
NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEA26hjntVPZMiwh4d8tyuk9KiucvG92BVUGArk5zO1jhmq7tLFgU1mqcIg
VGumfQqjkAzIuh83kxIiqBrB05Wvxp85apwt4sUCvzMe8mQWzZZZYp0rBzwpOj+VC5pxsMRYtYW+
BaTFBEmvFr7D7C7roZUk0lDppS5SZFs4SQbEe9ykB9aeUf1iTiw2+ikyP2+JEYto14WYCoxFWbms
FbQ1uaaK+yn1WH2YHhyMfi0IOxuT0jtbsngjHJMpWIqq334zBhj+rPSUug47YBHr41FCDMHbbbjv
WbyTyDYneOW3WY8LY8bGWVlAknQGB7lgduShe6e0RI/7SL/VE6X27lM9LwIDAQABozIwMDAgBgNV
HREEGTAXgRVsYXJzLmVnZ2VydEBub2tpYS5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUF
AAOBgQCx3nxxTg/WowobVTRXBiXUEEZj4LBiunWbuAnR0UbJIgijvq3JbiJvZo2gUGiW9LPaHSBz
4oxT1VR/S/6O0a4e87oV5cOQm6ReB68o9rDfUzxHTwoCfv2wwMwBrXyzQMjyQK4Lt8siV41gmZpm
rSXMhjTJdd9uYYNoZKQLq+VM+TCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG
A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMg
RGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3
DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3
MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9
fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+
uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMB
Af8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgG
A1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcP
f6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH
2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8x
ggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAo
UHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
a3GQsUdC7WDruGWZh/A+4jAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB
MBwGCSqGSIb3DQEJBTEPFw0wNzA4MjMxNDMxMTNaMCMGCSqGSIb3DQEJBDEWBBT7/qfHrfhFzKxa
kOXJcOwCecnzYTCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIwgYcGCyqGSIb3DQEJEAILMXigdjBiMQsw
CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE
AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEGtxkLFHQu1g67hlmYfwPuIw
DQYJKoZIhvcNAQEBBQAEggEAnODXe251Us4UM4Z31VkrCDmiH9SXaG/SQHnVg4eImoxItpdm2Dmb
M0RqJsj72YDmnc0t8MTVYAOl29xXOOGkaJuPK8u2L4SXktJmiv8DT4sHvANEe3Krz+AkwnXCOlyv
cqP4psS7znKJFLb+q0vWd+Pjyg++irDmlcrmvw9JYiwTbVOqj0mUWVKq/BARdQMsEYNd/PRFs9QB
KCeDuYN7ayT5UCko6zOgdjCnHEZcVq+0l3kPh55ppxu5+mutgWxycYlmvaNkwubuIGqreOkdCrqc
6tvgzjNfZmRv/xFi8ZzKE6hi/Z5IKnjJKUCmW28/meS7JxlXyUqUleqTTw3fGAAAAAAAAA==

--Apple-Mail-62--881124343--





From tsvwg-bounces@ietf.org Sun Aug 26 14:30:57 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPMr4-0000jK-6M; Sun, 26 Aug 2007 14:28:58 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IPMr2-0000j0-Q4
	for tsvwg-confirm+ok@megatron.ietf.org; Sun, 26 Aug 2007 14:28:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPMr2-0000ii-EU; Sun, 26 Aug 2007 14:28:56 -0400
Received: from [202.99.23.227] (helo=people.com.cn)
	by chiedprmail1.ietf.org with smtp (Exim 4.43)
	id 1IPMr1-0000wm-FP; Sun, 26 Aug 2007 14:28:56 -0400
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jme346d1e6a2; Mon, 27 Aug 2007 02:40:41 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id jm8346cd5010; Thr, 23 Aug 2007 08:40:12 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id AISP action; Thr, 23 Aug 2007 08:40:12 +0800
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IO0UM-0003ES-Uo; Wed, 22 Aug 2007 20:23:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IO0UH-0003Bi-1g; Wed, 22 Aug 2007 20:23:49 -0400
Received: from bosco.isi.edu ([128.9.168.207])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IO0UG-0006YQ-IH; Wed, 22 Aug 2007 20:23:48 -0400
Received: by bosco.isi.edu (Postfix, from userid 70)
	id 24391DFF54; Wed, 22 Aug 2007 17:22:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20070823002223.24391DFF54@bosco.isi.edu>
Date: Wed, 22 Aug 2007 17:22:23 -0700 (PDT)
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: ietf-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: rfc-editor@rfc-editor.org
X-Auto-Forward: jaglee@people.com.cn
 jag@kw.com.cn
X-Spam-Score: 2.8 (++)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [Tsvwg] BCP 133,
	RFC 5033 on Specifying New Congestion Control Algorithms
X-BeenThere: tsvwg@ietf.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


A new Request for Comments is now available in online RFC libraries.

        BCP 133        
        RFC 5033

        Title:      Specifying New Congestion Control Algorithms 
        Author:     S. Floyd, M. Allman
        Status:     Best Current Practice
        Date:       August 2007
        Mailbox:    floyd@icir.org, 
                    mallman@icir.org
        Pages:      10
        Characters: 23469
        Updates:    
        See-Also:   BCP0133

        I-D Tag:    draft-ietf-tsvwg-cc-alt-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5033.txt

The IETF's standard congestion control schemes have been widely
shown to be inadequate for various environments (e.g., high-speed
networks).  Recent research has yielded many alternate congestion
control schemes that significantly differ from the IETF's congestion
control principles.  Using these new congestion control schemes in
the global Internet has possible ramifications to both the traffic
using the new congestion control and to traffic using the currently
standardized congestion control.  Therefore, the IETF must proceed
with caution when dealing with alternate congestion control
proposals.  The goal of this document is to provide guidance for
considering alternate congestion control algorithms within the IETF.  
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.

This document is a product of the Transport Area Working Group
Working Group of the IETF.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce





From tsvwg-bounces@ietf.org Mon Aug 27 11:06:44 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPg9C-0007Z9-Iv; Mon, 27 Aug 2007 11:04:58 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IPg9A-0007Xa-B0
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 27 Aug 2007 11:04:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPg99-0007X2-UV; Mon, 27 Aug 2007 11:04:56 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IPg98-00077c-Eg; Mon, 27 Aug 2007 11:04:55 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	C8653207B1; Mon, 27 Aug 2007 17:04:47 +0200 (CEST)
X-AuditID: c1b4fb3c-b1e82bb0000007e1-c3-46d2e80fde06
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9C94C20671; Mon, 27 Aug 2007 17:04:47 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Aug 2007 17:04:46 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Aug 2007 17:04:46 +0200
Message-ID: <46D2E80E.8000001@ericsson.com>
Date: Mon, 27 Aug 2007 17:04:46 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <46AF5370.9020304@ericsson.com>
In-Reply-To: <46AF5370.9020304@ericsson.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
X-OriginalArrivalTime: 27 Aug 2007 15:04:46.0546 (UTC)
	FILETIME=[9B4E0B20:01C7E8BB]
X-Brightmail-Tracker: AAAAAA==
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9f79b8e383fd3af2b1b5b1d0910f6094
Cc: sip@ietf.org, IETF SIPPING WG <sipping@ietf.org>, tsvwg <tsvwg@ietf.org>,
	NSIS <nsis@ietf.org>
Subject: [Tsvwg] Re: Draft Liaison response to SG13 on Emergency
	Telecommunications
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi,

I have now updated this liaison reply to take the comments into account.=20
According to the ECRIT chairs they don't think what they are working is=20
related to the ongoing work Q.3/13 is working on. If you have any final=20
comments please provide them no later then the Wednesday 29th at 16.00 CE=
ST.

Magnus Westerlund


Submission
Date:		<tbd>, 2007

From: 		IETF Working groups TSVWG, NSIS, SIP and SIPPING

To:		Georges Sebek  <tsbsg13@itu.int> ,
		Keith Knightson <kgk@igs.net>

Cc:		Magnus Westerlund <magnus.westerlund@ericsson.com>,
                 Lars Eggert <lars.eggert@nokia.com>,
                 James Polk <jmpolk@cisco.com>,
                 Martin Stiemerling <stiemerling@netlab.nec.de>,
                 John Loughney <john.loughney@nokia.com>
                 Dean Willis <dean.willis@softarmor.com>,
                 Keith Drage <drage@alcatel-lucent.com>,
                 Mary Barnes <mary.barnes@nortel.com>,
                 Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>,
                 Scott Bradner <sob@harvard.edu>,
                 Kimberly King <ksking@mitre.org>,
                 Scott Brim <swb@employees.org>

Response
Contact:	TSV WG (tsv-chairs@tools.ietf.org)
		NSIS (nsis-chairs@tools.ietf.org)
		SIPPING (sipping-chairs@tools.ietf.org)
		SIP (sip-chairs@tools.ietf.org)
	=09
Purpose: 	Response to Liaison Request

Deadline:	None

Title: Response to liaison request from ITU-T Study Group 13 work on=20
emergency telecommunications

This is a response to the liaison request made by Q.3/13 regarding=20
emergency telecommunications (REF: NGN-GSI/DOC =E2=80=93 60 Rev.2). We wo=
uld=20
first like to apologize for failing to meet the deadline in responding.=20
We do hope that the late answer still can be of some use.

The liaison request was made to the following working groups (WG):=20
IEPREP, TSVWG, and NSIS. Since the request was sent the IEPREP WG has=20
concluded. In addition to the WGs from which information was requested,=20
we also think that work performed by the SIP and SIPPING WG may be of=20
relevance.

Pursuant to ITU-T Study Group 13 request for information on relevant and=20
related work in the IETF regarding emergency communications, we list=20
below RFCs and works in progress that we feel may be of interest to your=20
group.  Some of the completed work is Informational, and others are in=20
the category of Standards Track.

Q.3/13 also requested that we keep you informed of any developments in=20
regards to emergency telecommunications. In those regards we would like=20
to make you aware that IETF mailing list participation and document=20
information is free and open to anyone, allowing participants in Q.3/13=20
to keep themselves informed of any developments. If Q.3/13 desire to get=20
further information about specific ongoing work, then please send a=20
liaison request to the responsible WG for those specific documents.

The following list is divided under the associated working groups from=20
which the work has been done within the IETF.


SIP Working Group

RFC 4411

Title:
    Extending the Session Initiation Protocol (SIP)
    Reason Header for Preemption Events

Abstract:
   This document proposes an IANA Registration extension to the Session
    Initiation Protocol (SIP) Reason Header to be included in a BYE
    Method Request as a result of a session preemption event, either at a
    user agent (UA), or somewhere in the network involving a
    reservation-based protocol such as the Resource ReSerVation Protocol
    (RSVP) or Next Steps in Signaling (NSIS).  This document does not
    attempt to address routers failing in the packet path; instead, it
    addresses a deliberate tear down of a flow between UAs, and informs
    the terminated UA(s) with an indication of what occurred.

RFC 4412

Title:
    Communications Resource Priority for the Session Initiation
    Protocol (SIP)

Abstract:
    This document defines two new Session Initiation Protocol (SIP)
    header fields for communicating resource priority, namely,
    "Resource-Priority" and "Accept-Resource-Priority".  The
    "Resource-Priority" header field can influence the behavior of SIP
    user agents (such as telephone gateways and IP telephones) and SIP
    proxies.  It does not directly influence the forwarding behavior of
    IP routers.



SIPPING Working Group

	The below two documents are proposed work items accepted to become IETF=20
WG items are likely of interest as they update RFC 4412.

Work In Progress:   draft-polk-sip-rph-in-responses-00

Title:
Allowing SIP Resource Priority Header in SIP Responses

Abstract:
    The Session Initiation Protocol (SIP) Resource Priority Header
    (RPH), in its current form, is ignored in SIP responses.  This was a
    design choice during RFC 4412's development. This is now considered
    a bad design choice in certain scenarios.  This document corrects
    RFC 4412's communications model by optionally allowing a SIP server
    or user agent client to process the Resource-Priority Header in a
    response.

Work In Progress:   draft-polk-sip-rph-new-namespaces--00

Title:
New Session Initiation Protocol Resource-Priority Header Namespaces for=20
the Defense Information Systems Agency

Abstract:
    This document creates additional Session Initiation Protocol
    Resource-Priority header namespaces, to be IANA registered.  This
    document intends to update RFC 4412, as a Proposed Standard document
    if published by the RFC-Editor.

IEPREP Working Group

RFC 3487

Title:
    Requirements for Resource Priority Mechanisms for the
    Session Initiation Protocol (SIP)

Abstract:
    This document summarizes requirements for prioritizing access to
    circuit-switched network, end system and proxy resources for
    emergency preparedness communications using the Session Initiation
    Protocol (SIP).

RFC 3689

Title:
    General Requirements for
    Emergency Telecommunication Service (ETS)

Abstract:
    This document presents a list of general requirements in support of
    Emergency Telecommunications Service (ETS).  Solutions to these
    requirements are not presented in this document.  Additional
    requirements pertaining to specific applications, or types of
    applications, are to be specified in separate document(s).

RFC 3690

Title:
    IP Telephony Requirements for
    Emergency Telecommunication Service (ETS)

Abstract:
    This document presents a list of requirements in support of Emergency
    Telecommunications Service (ETS) within the context of IP telephony.
    It is an extension to the general requirements presented in RFC 3689.
    Solutions to these requirements are not presented in this document.

RFC 4190

Title:
    Framework for Supporting Emergency Telecommunications
    Service (ETS) in IP Telephony

Abstract:
    This document presents a framework for supporting authorized,
    emergency-related communication within the context of IP telephony.
    We present a series of objectives that reflect a general view of how
    authorized emergency service, in line with the Emergency
    Telecommunications Service (ETS), should be realized within today's
    IP architecture and service models.  From these objectives, we
    present a corresponding set of protocols and capabilities, which
    provide a more specific set of recommendations regarding existing
    IETF protocols.  Finally, we present two scenarios that act as
    guiding models for the objectives and functions listed in this
    document.  These models, coupled with an example of an existing
    service in the Public Switched Telephone Network (PSTN), contribute
    to a constrained solution space.

RFC 4375

Title:
    Emergency Telecommunications Services (ETS) Requirements
    for a Single Administrative Domain

Abstract:
    This document presents a list of requirements in support of Emergency
    Telecommunications Service (ETS) within a single administrative
    domain.  This document focuses on a specific set of administrative
    constraints and scope.  Solutions to these requirements are not
    presented in this document.


TSV Working Group

RFC 4542

Title:
    Implementing an Emergency Telecommunications Service (ETS)
    for Real-Time Services in the Internet Protocol Suite

Abstract:
    RFCs 3689 and 3690 detail requirements for an Emergency
    Telecommunications Service (ETS), of which an Internet Emergency
    Preparedness Service (IEPS) would be a part.  Some of these types of
    services require call preemption; others require call queuing or
    other mechanisms.  IEPS requires a Call Admission Control (CAC)
    procedure and a Per Hop Behavior (PHB) for the data that meet the
    needs of this architecture.  Such a CAC procedure and PHB is
    appropriate to any service that might use H.323 or SIP to set up
    real-time sessions.  The key requirement is to guarantee an elevated
    probability of call completion to an authorized user in time of
    crisis.

    This document primarily discusses supporting ETS in the context of
    the US Government and NATO, because it focuses on the Multi-Level
    Precedence and Preemption (MLPP) and Government Emergency
    Telecommunication Service (GETS) standards.  The architectures
    described here are applicable beyond these organizations.

Work In Progress:   draft-ietf-tsvwg-emergency-rsvp-03.txt

Title:
    Resource ReSerVation Protovol (RSVP) Extensions for
    Emergency Services

Abstract:
    An Emergency Telecommunications Service (ETS) requires the ability to
    provide an elevated probability of session establishment to an
    authorized user in times of network congestion (typically, during a
    crisis). When supported over the Internet Protocol suite, this may be
    facilitated through a network layer admission control solution, which
    supports prioritized access to resources (e.g., bandwidth). These
    resources may be explicitly set aside for emergency services, or they
    may be shared with other sessions.

   This document specifies RSVP extensions that can be used to support
    such an admission priority capability at the network layer. Note that
    these extensions represent one possible solution component in
    satisfying ETS requirements. Other solution components, or other
    solutions, are outside the scope of this document.

NSIS Working Group

Work In Progress: draft-ietf-nsis-qos-nslp-14.txt

Title:
NSLP for Quality-of-Service Signaling

Abstract:
This specification describes the NSIS Signaling Layer Protocol (NSLP)=20
for signaling QoS reservations in the Internet.  It is in accordance=20
with the framework and requirements developed in NSIS.  Together with=20
GIST, it provides functionality similar to RSVP and extends it.  The QoS=20
NSLP is independent of the underlying QoS specification or architecture=20
and provides support for different reservation models. It is simplified=20
by the elimination of support for multicast flows. This specification=20
explains the overall protocol approach, design decisions made and=20
provides examples.  It specifies object, message  formats and processing=20
rules.

Non-WG Documents

	Approved for publication: draft-carlberg-trip-attribute-rp-02.txt

	Title:
	  TRIP Attribute for Resource Priority
=09
Abstract:
    This document defines a new attribute for  the  TRIP  protocol.   The
    attribute   associates   protocols/services   in  the  PSTN  offering
    authorized  prioritization  during  call  setup  that  are  reachable
    through  a TRIP gateway.  Current examples of preferential service in
    the PSTN are Government Emergency Telecommunications  Service  (GETS)
    in  the U.S. and Government Telephone Preference Scheme (GTPS) in the
    U.K.  The proposed attribute for TRIP is based on the NameSpace.Value
    tupple defined for the SIP resource Priority field.



--=20

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------





From tsvwg-bounces@ietf.org Mon Aug 27 13:45:59 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPidI-0002L2-Qa; Mon, 27 Aug 2007 13:44:12 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IPidH-0002J7-GB
	for tsvwg-confirm+ok@megatron.ietf.org; Mon, 27 Aug 2007 13:44:11 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPidG-0002Ii-Pa; Mon, 27 Aug 2007 13:44:10 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IPidF-0003fu-6e; Mon, 27 Aug 2007 13:44:10 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-4.cisco.com with ESMTP; 27 Aug 2007 10:44:08 -0700
X-IronPort-AV: i="4.19,312,1183359600"; d="scan'208"; a="8948966:sNHT37752318"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7RHi8I9018831; 
	Mon, 27 Aug 2007 10:44:08 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7RHi7lH024692;
	Mon, 27 Aug 2007 17:44:08 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Aug 2007 10:43:58 -0700
Received: from jmpolk-wxp.cisco.com ([10.21.91.203]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Aug 2007 10:43:58 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 27 Aug 2007 12:43:56 -0500
To: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <46D2E80E.8000001@ericsson.com>
References: <46AF5370.9020304@ericsson.com>
 <46D2E80E.8000001@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Message-ID: <XFE-SJC-211IFprhMOg0000051a@xfe-sjc-211.amer.cisco.com>
X-OriginalArrivalTime: 27 Aug 2007 17:43:58.0357 (UTC)
	FILETIME=[D8A0BC50:01C7E8D1]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=13773; t=1188236648;
	x=1189100648; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jmpolk@cisco.com;
	z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Re=3A=20Draft=20Liaison=20response=20to=20SG1
	3=20on=20Emergency=0A=20=20Telecommunications |Sender:=20;
	bh=sD60hnFy/1jeEK1NSSply5RPrbOwmB6enSRDS4sAZwA=;
	b=NJ5rCWq1ZGUUY+eJFusmZiG9HMDYbUGWMPHFX+snThPELoZWBHziyWTEWKUzwvNCia6c+Xib
	Su+2TerJMq4GI4YlehPPQ+olRzN0EU6a4fDGso7kncfj3xpvjujDn5RU;
Authentication-Results: sj-dkim-2; header.From=jmpolk@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8921dd2ebcb07edebf7bfaf4808c2ad
Cc: sip@ietf.org, IETF SIPPING WG <sipping@ietf.org>, tsvwg <tsvwg@ietf.org>,
	NSIS <nsis@ietf.org>
Subject: [Tsvwg] Re: [Sip] Re: Draft Liaison response to SG13 on Emergency
 Telecommunications
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Magnus

comments in-line below about from which WG certain documents originated

At 10:04 AM 8/27/2007, Magnus Westerlund wrote:
>Hi,
>
>I have now updated this liaison reply to take=20
>the comments into account. According to the=20
>ECRIT chairs they don't think what they are=20
>working is related to the ongoing work Q.3/13 is=20
>working on. If you have any final comments=20
>please provide them no later then the Wednesday 29th at 16.00 CEST.
>
>Magnus Westerlund
>
>
>Submission
>Date:           <tbd>, 2007
>
>From:           IETF Working groups TSVWG, NSIS, SIP and SIPPING
>
>To:             Georges Sebek  <tsbsg13@itu.int> ,
>                 Keith Knightson <kgk@igs.net>
>
>Cc:             Magnus Westerlund <magnus.westerlund@ericsson.com>,
>                 Lars Eggert <lars.eggert@nokia.com>,
>                 James Polk <jmpolk@cisco.com>,
>                 Martin Stiemerling <stiemerling@netlab.nec.de>,
>                 John Loughney <john.loughney@nokia.com>
>                 Dean Willis <dean.willis@softarmor.com>,
>                 Keith Drage <drage@alcatel-lucent.com>,
>                 Mary Barnes <mary.barnes@nortel.com>,
>                 Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>,
>                 Scott Bradner <sob@harvard.edu>,
>                 Kimberly King <ksking@mitre.org>,
>                 Scott Brim <swb@employees.org>
>
>Response
>Contact:        TSV WG (tsv-chairs@tools.ietf.org)
>                 NSIS (nsis-chairs@tools.ietf.org)
>                 SIPPING (sipping-chairs@tools.ietf.org)
>                 SIP (sip-chairs@tools.ietf.org)
>
>Purpose:        Response to Liaison Request
>
>Deadline:       None
>
>Title: Response to liaison request from ITU-T=20
>Study Group 13 work on emergency telecommunications
>
>This is a response to the liaison request made=20
>by Q.3/13 regarding emergency telecommunications=20
>(REF: NGN-GSI/DOC =AD 60 Rev.2). We woould first=20
>like to apologize for failing to meet the=20
>deadline in responding. We do hope that the late=20
>answer still can be of some use.
>
>The liaison request was made to the following=20
>working groups (WG): IEPREP, TSVWG, and NSIS.=20
>Since the request was sent the IEPREP WG has=20
>concluded. In addition to the WGs from which=20
>information was requested, we also think that=20
>work performed by the SIP and SIPPING WG may be of relevance.
>
>Pursuant to ITU-T Study Group 13 request for=20
>information on relevant and related work in the=20
>IETF regarding emergency communications, we list=20
>below RFCs and works in progress that we feel=20
>may be of interest to your group.  Some of the=20
>completed work is Informational, and others are=20
>in the category of Standards Track.
>
>Q.3/13 also requested that we keep you informed=20
>of any developments in regards to emergency=20
>telecommunications. In those regards we would=20
>like to make you aware that IETF mailing list=20
>participation and document information is free=20
>and open to anyone, allowing participants in=20
>Q.3/13 to keep themselves informed of any=20
>developments. If Q.3/13 desire to get further=20
>information about specific ongoing work, then=20
>please send a liaison request to the responsible=20
>WG for those specific documents.
>
>The following list is divided under the=20
>associated working groups from which the work has been done within the=
 IETF.
>
>
>SIP Working Group
>
>RFC 4411

RFC4411 is from SIPPING


>Title:
>    Extending the Session Initiation Protocol (SIP)
>    Reason Header for Preemption Events
>
>Abstract:
>   This document proposes an IANA Registration extension to the Session
>    Initiation Protocol (SIP) Reason Header to be included in a BYE
>    Method Request as a result of a session preemption event, either at a
>    user agent (UA), or somewhere in the network involving a
>    reservation-based protocol such as the Resource ReSerVation Protocol
>    (RSVP) or Next Steps in Signaling (NSIS).  This document does not
>    attempt to address routers failing in the packet path; instead, it
>    addresses a deliberate tear down of a flow between UAs, and informs
>    the terminated UA(s) with an indication of what occurred.
>
>RFC 4412
>
>Title:
>    Communications Resource Priority for the Session Initiation
>    Protocol (SIP)
>
>Abstract:
>    This document defines two new Session Initiation Protocol (SIP)
>    header fields for communicating resource priority, namely,
>    "Resource-Priority" and "Accept-Resource-Priority".  The
>    "Resource-Priority" header field can influence the behavior of SIP
>    user agents (such as telephone gateways and IP telephones) and SIP
>    proxies.  It does not directly influence the forwarding behavior of
>    IP routers.
>
>
>
>SIPPING Working Group

both IDs below are SIP WG items, not SIPPING


>         The below two documents are proposed=20
> work items accepted to become IETF WG items are=20
> likely of interest as they update RFC 4412.
>
>Work In Progress:   draft-polk-sip-rph-in-responses-00
>
>Title:
>Allowing SIP Resource Priority Header in SIP Responses
>
>Abstract:
>    The Session Initiation Protocol (SIP) Resource Priority Header
>    (RPH), in its current form, is ignored in SIP responses.  This was a
>    design choice during RFC 4412's development. This is now considered
>    a bad design choice in certain scenarios.  This document corrects
>    RFC 4412's communications model by optionally allowing a SIP server
>    or user agent client to process the Resource-Priority Header in a
>    response.
>
>Work In Progress:   draft-polk-sip-rph-new-namespaces--00
>
>Title:
>New Session Initiation Protocol=20
>Resource-Priority Header Namespaces for the Defense Information Systems=
 Agency
>
>Abstract:
>    This document creates additional Session Initiation Protocol
>    Resource-Priority header namespaces, to be IANA registered.  This
>    document intends to update RFC 4412, as a Proposed Standard document
>    if published by the RFC-Editor.
>
>IEPREP Working Group
>
>RFC 3487
>
>Title:
>    Requirements for Resource Priority Mechanisms for the
>    Session Initiation Protocol (SIP)
>
>Abstract:
>    This document summarizes requirements for prioritizing access to
>    circuit-switched network, end system and proxy resources for
>    emergency preparedness communications using the Session Initiation
>    Protocol (SIP).
>
>RFC 3689
>
>Title:
>    General Requirements for
>    Emergency Telecommunication Service (ETS)
>
>Abstract:
>    This document presents a list of general requirements in support of
>    Emergency Telecommunications Service (ETS).  Solutions to these
>    requirements are not presented in this document.  Additional
>    requirements pertaining to specific applications, or types of
>    applications, are to be specified in separate document(s).
>
>RFC 3690
>
>Title:
>    IP Telephony Requirements for
>    Emergency Telecommunication Service (ETS)
>
>Abstract:
>    This document presents a list of requirements in support of Emergency
>    Telecommunications Service (ETS) within the context of IP telephony.
>    It is an extension to the general requirements presented in RFC 3689.
>    Solutions to these requirements are not presented in this document.
>
>RFC 4190
>
>Title:
>    Framework for Supporting Emergency Telecommunications
>    Service (ETS) in IP Telephony
>
>Abstract:
>    This document presents a framework for supporting authorized,
>    emergency-related communication within the context of IP telephony.
>    We present a series of objectives that reflect a general view of how
>    authorized emergency service, in line with the Emergency
>    Telecommunications Service (ETS), should be realized within today's
>    IP architecture and service models.  From these objectives, we
>    present a corresponding set of protocols and capabilities, which
>    provide a more specific set of recommendations regarding existing
>    IETF protocols.  Finally, we present two scenarios that act as
>    guiding models for the objectives and functions listed in this
>    document.  These models, coupled with an example of an existing
>    service in the Public Switched Telephone Network (PSTN), contribute
>    to a constrained solution space.
>
>RFC 4375
>
>Title:
>    Emergency Telecommunications Services (ETS) Requirements
>    for a Single Administrative Domain
>
>Abstract:
>    This document presents a list of requirements in support of Emergency
>    Telecommunications Service (ETS) within a single administrative
>    domain.  This document focuses on a specific set of administrative
>    constraints and scope.  Solutions to these requirements are not
>    presented in this document.
>
>
>TSV Working Group
>
>RFC 4542
>
>Title:
>    Implementing an Emergency Telecommunications Service (ETS)
>    for Real-Time Services in the Internet Protocol Suite
>
>Abstract:
>    RFCs 3689 and 3690 detail requirements for an Emergency
>    Telecommunications Service (ETS), of which an Internet Emergency
>    Preparedness Service (IEPS) would be a part.  Some of these types of
>    services require call preemption; others require call queuing or
>    other mechanisms.  IEPS requires a Call Admission Control (CAC)
>    procedure and a Per Hop Behavior (PHB) for the data that meet the
>    needs of this architecture.  Such a CAC procedure and PHB is
>    appropriate to any service that might use H.323 or SIP to set up
>    real-time sessions.  The key requirement is to guarantee an elevated
>    probability of call completion to an authorized user in time of
>    crisis.
>
>    This document primarily discusses supporting ETS in the context of
>    the US Government and NATO, because it focuses on the Multi-Level
>    Precedence and Preemption (MLPP) and Government Emergency
>    Telecommunication Service (GETS) standards.  The architectures
>    described here are applicable beyond these organizations.
>
>Work In Progress:   draft-ietf-tsvwg-emergency-rsvp-03.txt
>
>Title:
>    Resource ReSerVation Protovol (RSVP) Extensions for
>    Emergency Services
>
>Abstract:
>    An Emergency Telecommunications Service (ETS) requires the ability to
>    provide an elevated probability of session establishment to an
>    authorized user in times of network congestion (typically, during a
>    crisis). When supported over the Internet Protocol suite, this may be
>    facilitated through a network layer admission control solution, which
>    supports prioritized access to resources (e.g., bandwidth). These
>    resources may be explicitly set aside for emergency services, or they
>    may be shared with other sessions.
>
>   This document specifies RSVP extensions that can be used to support
>    such an admission priority capability at the network layer. Note that
>    these extensions represent one possible solution component in
>    satisfying ETS requirements. Other solution components, or other
>    solutions, are outside the scope of this document.
>
>NSIS Working Group
>
>Work In Progress: draft-ietf-nsis-qos-nslp-14.txt
>
>Title:
>NSLP for Quality-of-Service Signaling
>
>Abstract:
>This specification describes the NSIS Signaling=20
>Layer Protocol (NSLP) for signaling QoS=20
>reservations in the Internet.  It is in=20
>accordance with the framework and requirements=20
>developed in NSIS.  Together with GIST, it=20
>provides functionality similar to RSVP and=20
>extends it.  The QoS NSLP is independent of the=20
>underlying QoS specification or architecture and=20
>provides support for different reservation=20
>models. It is simplified by the elimination of=20
>support for multicast flows. This specification=20
>explains the overall protocol approach, design=20
>decisions made and provides examples.  It=20
>specifies object, message  formats and processing rules.
>
>Non-WG Documents
>
>         Approved for publication: draft-carlberg-trip-attribute-rp-02.txt
>
>         Title:
>           TRIP Attribute for Resource Priority
>
>Abstract:
>    This document defines a new attribute for  the  TRIP  protocol.   The
>    attribute   associates   protocols/services   in  the  PSTN  offering
>    authorized  prioritization  during  call  setup  that  are  reachable
>    through  a TRIP gateway.  Current examples of preferential service in
>    the PSTN are Government Emergency Telecommunications  Service  (GETS)
>    in  the U.S. and Government Telephone Preference Scheme (GTPS) in the
>    U.K.  The proposed attribute for TRIP is based on the NameSpace.Value
>    tupple defined for the SIP resource Priority field.
>
>
>
>--
>
>Magnus Westerlund
>
>IETF Transport Area Director & TSVWG Chair
>----------------------------------------------------------------------
>Multimedia Technologies, Ericsson Research EAB/TVM/M
>----------------------------------------------------------------------
>Ericsson AB                | Phone +46 8 4048287
>Torshamsgatan 23           | Fax   +46 8 7575550
>S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>----------------------------------------------------------------------
>
>
>_______________________________________________
>Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sipping@ietf.org for new developments on the application of sip





From tsvwg-bounces@ietf.org Tue Aug 28 03:35:30 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPva3-0007BA-Hs; Tue, 28 Aug 2007 03:33:43 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IPva2-0007Aa-4w
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 28 Aug 2007 03:33:42 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPvZy-00078U-2t; Tue, 28 Aug 2007 03:33:38 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IPvZw-0008UK-Bj; Tue, 28 Aug 2007 03:33:37 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	B1B9C210F1; Tue, 28 Aug 2007 09:33:35 +0200 (CEST)
X-AuditID: c1b4fb3e-b0835bb0000007e1-42-46d3cfcfa7e9
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7CCBF203FB; Tue, 28 Aug 2007 09:33:35 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Aug 2007 09:33:35 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Aug 2007 09:33:35 +0200
Message-ID: <46D3CFCF.6070308@ericsson.com>
Date: Tue, 28 Aug 2007 09:33:35 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
Subject: Re: [Tsvwg] Re: [Sip] Re: Draft Liaison response to SG13 on Emergency
	Telecommunications
References: <46AF5370.9020304@ericsson.com> <46D2E80E.8000001@ericsson.com>
	<XFE-SJC-211IFprhMOg0000051a@xfe-sjc-211.amer.cisco.com>
In-Reply-To: <XFE-SJC-211IFprhMOg0000051a@xfe-sjc-211.amer.cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
X-OriginalArrivalTime: 28 Aug 2007 07:33:35.0545 (UTC)
	FILETIME=[BE24DA90:01C7E945]
X-Brightmail-Tracker: AAAAAA==
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 4d9ae72af46718088458d214998cc683
Cc: sip@ietf.org, dime@ietf.org, IETF SIPPING WG <sipping@ietf.org>,
	tsvwg <tsvwg@ietf.org>, NSIS <nsis@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi again,

I have received some more comments. So here is an updated version adding=20
DIME documents and correcting origin of documents.


Submission
Date:		<tbd>, 2007

From: 		IETF Working groups TSVWG, NSIS, DIME, SIP and SIPPING

To:		Georges Sebek  <tsbsg13@itu.int> ,
		Keith Knightson <kgk@igs.net>

Cc:		Magnus Westerlund <magnus.westerlund@ericsson.com>,
Lars Eggert <lars.eggert@nokia.com>,
James Polk <jmpolk@cisco.com>,
Martin Stiemerling <stiemerling@netlab.nec.de>,
John Loughney <john.loughney@nokia.com>
Dean Willis <dean.willis@softarmor.com>,
Keith Drage <drage@alcatel-lucent.com>,
Mary Barnes <mary.barnes@nortel.com>,
Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>,
Scott Bradner <sob@harvard.edu>,
Kimberly King <ksking@mitre.org>,
Scott Brim <swb@employees.org>,
Hannes Tschofenig <Hannes.Tschofenig@gmx.net>,
David Frascone <dave@frascone.com>

Response
Contact:	TSV WG (tsv-chairs@tools.ietf.org)
		NSIS (nsis-chairs@tools.ietf.org)
		SIPPING (sipping-chairs@tools.ietf.org)
		SIP (sip-chairs@tools.ietf.org)
		DIME (dime-chairs@tools.ietf.org)
	=09
Purpose: 	Response to Liaison Request

Deadline:	None

Title: Response to liaison request from ITU-T Study Group 13 work on=20
emergency telecommunications

This is a response to the liaison request made by Q.3/13 regarding=20
emergency telecommunications (REF: NGN-GSI/DOC =96 60 Rev.2). We would=20
first like to apologize for failing to meet the deadline in responding.=20
We do hope that the late answer still can be of some use.

The liaison request was made to the following working groups (WG):=20
IEPREP, TSVWG, and NSIS. Since the request was sent the IEPREP WG has=20
concluded. In addition to the WGs from which information was requested,=20
we also think that work performed by the DIME, SIP and SIPPING WG may be=20
of relevance.

Pursuant to ITU-T Study Group 13 request for information on relevant and=20
related work in the IETF regarding emergency communications, we list=20
below RFCs and works in progress that we feel may be of interest to your=20
group.  Some of the completed work is Informational, and others are in=20
the category of Standards Track.

Q.3/13 also requested that we keep you informed of any developments in=20
regards to emergency telecommunications. In those regards we would like=20
to make you aware that IETF mailing list participation and document=20
information is free and open to anyone, allowing participants in Q.3/13=20
to keep themselves informed of any developments. If Q.3/13 desire to get=20
further information about specific ongoing work, then please send a=20
liaison request to the responsible WG for those specific documents.

The following list is divided under the associated working groups from=20
which the work has been done within the IETF.


SIP Working Group

RFC 4412

Title:
    Communications Resource Priority for the Session Initiation
    Protocol (SIP)

Abstract:
    This document defines two new Session Initiation Protocol (SIP)
    header fields for communicating resource priority, namely,
    "Resource-Priority" and "Accept-Resource-Priority".  The
    "Resource-Priority" header field can influence the behavior of SIP
    user agents (such as telephone gateways and IP telephones) and SIP
    proxies.  It does not directly influence the forwarding behavior of
    IP routers.

	The below two documents are proposed work items accepted to become IETF=20
WG items are likely of interest as they update RFC 4412.

Work In Progress:   draft-polk-sip-rph-in-responses-00

Title:
Allowing SIP Resource Priority Header in SIP Responses

Abstract:
    The Session Initiation Protocol (SIP) Resource Priority Header
    (RPH), in its current form, is ignored in SIP responses.  This was a
    design choice during RFC 4412's development. This is now considered
    a bad design choice in certain scenarios.  This document corrects
    RFC 4412's communications model by optionally allowing a SIP server
    or user agent client to process the Resource-Priority Header in a
    response.

Work In Progress:   draft-polk-sip-rph-new-namespaces--00

Title:
New Session Initiation Protocol Resource-Priority Header Namespaces for=20
the Defense Information Systems Agency

Abstract:
    This document creates additional Session Initiation Protocol
    Resource-Priority header namespaces, to be IANA registered.  This
    document intends to update RFC 4412, as a Proposed Standard document
    if published by the RFC-Editor.



SIPPING Working Group

RFC 4411

Title:
    Extending the Session Initiation Protocol (SIP)
    Reason Header for Preemption Events

Abstract:
   This document proposes an IANA Registration extension to the Session
    Initiation Protocol (SIP) Reason Header to be included in a BYE
    Method Request as a result of a session preemption event, either at a
    user agent (UA), or somewhere in the network involving a
    reservation-based protocol such as the Resource ReSerVation Protocol
    (RSVP) or Next Steps in Signaling (NSIS).  This document does not
    attempt to address routers failing in the packet path; instead, it
    addresses a deliberate tear down of a flow between UAs, and informs
    the terminated UA(s) with an indication of what occurred.

IEPREP Working Group

RFC 3487

Title:
    Requirements for Resource Priority Mechanisms for the
    Session Initiation Protocol (SIP)

Abstract:
    This document summarizes requirements for prioritizing access to
    circuit-switched network, end system and proxy resources for
    emergency preparedness communications using the Session Initiation
    Protocol (SIP).

RFC 3689

Title:
    General Requirements for
    Emergency Telecommunication Service (ETS)

Abstract:
    This document presents a list of general requirements in support of
    Emergency Telecommunications Service (ETS).  Solutions to these
    requirements are not presented in this document.  Additional
    requirements pertaining to specific applications, or types of
    applications, are to be specified in separate document(s).

RFC 3690

Title:
    IP Telephony Requirements for
    Emergency Telecommunication Service (ETS)

Abstract:
    This document presents a list of requirements in support of Emergency
    Telecommunications Service (ETS) within the context of IP telephony.
    It is an extension to the general requirements presented in RFC 3689.
    Solutions to these requirements are not presented in this document.

RFC 4190

Title:
    Framework for Supporting Emergency Telecommunications
    Service (ETS) in IP Telephony

Abstract:
    This document presents a framework for supporting authorized,
    emergency-related communication within the context of IP telephony.
    We present a series of objectives that reflect a general view of how
    authorized emergency service, in line with the Emergency
    Telecommunications Service (ETS), should be realized within today's
    IP architecture and service models.  From these objectives, we
    present a corresponding set of protocols and capabilities, which
    provide a more specific set of recommendations regarding existing
    IETF protocols.  Finally, we present two scenarios that act as
    guiding models for the objectives and functions listed in this
    document.  These models, coupled with an example of an existing
    service in the Public Switched Telephone Network (PSTN), contribute
    to a constrained solution space.

RFC 4375

Title:
    Emergency Telecommunications Services (ETS) Requirements
    for a Single Administrative Domain

Abstract:
    This document presents a list of requirements in support of Emergency
    Telecommunications Service (ETS) within a single administrative
    domain.  This document focuses on a specific set of administrative
    constraints and scope.  Solutions to these requirements are not
    presented in this document.


TSV Working Group

RFC 4542

Title:
    Implementing an Emergency Telecommunications Service (ETS)
    for Real-Time Services in the Internet Protocol Suite

Abstract:
    RFCs 3689 and 3690 detail requirements for an Emergency
    Telecommunications Service (ETS), of which an Internet Emergency
    Preparedness Service (IEPS) would be a part.  Some of these types of
    services require call preemption; others require call queuing or
    other mechanisms.  IEPS requires a Call Admission Control (CAC)
    procedure and a Per Hop Behavior (PHB) for the data that meet the
    needs of this architecture.  Such a CAC procedure and PHB is
    appropriate to any service that might use H.323 or SIP to set up
    real-time sessions.  The key requirement is to guarantee an elevated
    probability of call completion to an authorized user in time of
    crisis.

    This document primarily discusses supporting ETS in the context of
    the US Government and NATO, because it focuses on the Multi-Level
    Precedence and Preemption (MLPP) and Government Emergency
    Telecommunication Service (GETS) standards.  The architectures
    described here are applicable beyond these organizations.

Work In Progress:   draft-ietf-tsvwg-emergency-rsvp-03.txt

Title:
    Resource ReSerVation Protovol (RSVP) Extensions for
    Emergency Services

Abstract:
    An Emergency Telecommunications Service (ETS) requires the ability to
    provide an elevated probability of session establishment to an
    authorized user in times of network congestion (typically, during a
    crisis). When supported over the Internet Protocol suite, this may be
    facilitated through a network layer admission control solution, which
    supports prioritized access to resources (e.g., bandwidth). These
    resources may be explicitly set aside for emergency services, or they
    may be shared with other sessions.

   This document specifies RSVP extensions that can be used to support
    such an admission priority capability at the network layer. Note that
    these extensions represent one possible solution component in
    satisfying ETS requirements. Other solution components, or other
    solutions, are outside the scope of this document.

NSIS Working Group

Work In Progress: draft-ietf-nsis-qos-nslp-14.txt

Title:
NSLP for Quality-of-Service Signaling

Abstract:
This specification describes the NSIS Signaling Layer Protocol (NSLP)=20
for signaling QoS reservations in the Internet.  It is in accordance=20
with the framework and requirements developed in NSIS.  Together with=20
GIST, it provides functionality similar to RSVP and extends it.  The QoS=20
NSLP is independent of the underlying QoS specification or architecture=20
and provides support for different reservation models. It is simplified=20
by the elimination of support for multicast flows. This specification=20
explains the overall protocol approach, design decisions made and=20
provides examples.  It specifies object, message  formats and processing=20
rules.

DIME Working Group

Work In Progress: draft-ietf-dime-diameter-qos-01.txt

Title:
   Diameter Quality of Service Application

Abstract:
   This document describes a Diameter application that performs
   Authentication, Authorization, and Accounting for Quality of Service
   (QoS) reservations.  This protocol is used by elements along the path
   of a given application flow to authenticate a reservation request,
   ensure that the reservation is authorized, and to account for
   resources consumed during the lifetime of the application flow.
   Clients that implement the Diameter QoS application contact an
   authorizing entity/application server that is located somewhere in
   the network, allowing for a wide variety of flexible deployment
   models.

Work In Progress: draft-ietf-dime-qos-parameters-00.txt

Title:
   Quality of Service Parameters for Usage with the AAA Framework

Abstract:
   This document defines a number of Quality of Service (QoS) parameters
   that can be reused for conveying QoS information within RADIUS and
   Diameter.

   The payloads used to carry these QoS parameters are opaque for the
   AAA client and the AAA server itself and interpreted by the
   respective Resource Management Function.

Work In Progress: draft-ietf-dime-qos-attributes-01.txt

Title:
   Quality of Service Attributes for Diameter and RADIUS

Abstract:
   This document extends the functionality of the Diameter Base protocol
   and other Diameter applications with respect to their ability to
   convey Quality of Service information.  The AVPs defined in this
   document are also available for Remote Authentication Dial In User
   Service (RADIUS).


Non-WG Documents

	Approved for publication: draft-carlberg-trip-attribute-rp-02.txt

	Title:
	  TRIP Attribute for Resource Priority
=09
Abstract:
    This document defines a new attribute for  the  TRIP  protocol.   The
    attribute   associates   protocols/services   in  the  PSTN  offering
    authorized  prioritization  during  call  setup  that  are  reachable
    through  a TRIP gateway.  Current examples of preferential service in
    the PSTN are Government Emergency Telecommunications  Service  (GETS)
    in  the U.S. and Government Telephone Preference Scheme (GTPS) in the
    U.K.  The proposed attribute for TRIP is based on the NameSpace.Value
    tupple defined for the SIP resource Priority field.




Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------





From tsvwg-bounces@ietf.org Tue Aug 28 03:57:36 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPvvR-0005nj-02; Tue, 28 Aug 2007 03:55:49 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IPvvO-0005n4-QE
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 28 Aug 2007 03:55:46 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPvvO-0005mj-4W; Tue, 28 Aug 2007 03:55:46 -0400
Received: from ccsmtpgate.mugla.edu.tr ([194.27.32.25]
	helo=ccsmtpgate.mu.edu.tr)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IPvvM-0000NA-1O; Tue, 28 Aug 2007 03:55:45 -0400
Received: from ccexc01.mu.edu.tr ([10.1.1.15]) by ccsmtpgate.mu.edu.tr with
	Microsoft SMTPSVC(6.0.3790.3959); Tue, 28 Aug 2007 11:01:48 +0300
Received: from mail pickup service by ccexc01.mu.edu.tr with Microsoft SMTPSVC;
	Tue, 28 Aug 2007 11:01:46 +0300
Received: from megatron.ietf.org ([156.154.16.145]) by ccsmtpgate.mu.edu.tr
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 28 Aug 2007 10:40:37 +0300
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPva6-0007Bz-N6; Tue, 28 Aug 2007 03:33:46 -0400
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1IPva3-0007B5-6x
	for nsis-confirm+ok@megatron.ietf.org; Tue, 28 Aug 2007 03:33:43 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPvZy-00078U-2t; Tue, 28 Aug 2007 03:33:38 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IPvZw-0008UK-Bj; Tue, 28 Aug 2007 03:33:37 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	B1B9C210F1; Tue, 28 Aug 2007 09:33:35 +0200 (CEST)
X-AuditID: c1b4fb3e-b0835bb0000007e1-42-46d3cfcfa7e9
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7CCBF203FB; Tue, 28 Aug 2007 09:33:35 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Aug 2007 09:33:35 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Aug 2007 09:33:35 +0200
Message-ID: <46D3CFCF.6070308@ericsson.com>
Date: Tue, 28 Aug 2007 09:33:35 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
References: <46AF5370.9020304@ericsson.com> <46D2E80E.8000001@ericsson.com>
	<XFE-SJC-211IFprhMOg0000051a@xfe-sjc-211.amer.cisco.com>
In-Reply-To: <XFE-SJC-211IFprhMOg0000051a@xfe-sjc-211.amer.cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
X-OriginalArrivalTime: 28 Aug 2007 07:33:35.0545 (UTC)
	FILETIME=[BE24DA90:01C7E945]
X-Brightmail-Tracker: AAAAAA==
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 4d9ae72af46718088458d214998cc683
Subject: [NSIS] Re: [Tsvwg] Re: [Sip] Re: Draft Liaison response to SG13 on
	Emergency Telecommunications
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 17cf8eab1d6bbd2874a56f9e3554d91d
Cc: sip@ietf.org, IETF SIPPING WG <sipping@ietf.org>, dime@ietf.org,
	tsvwg <tsvwg@ietf.org>, NSIS <nsis@ietf.org>
X-BeenThere: tsvwg@ietf.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi again,

I have received some more comments. So here is an updated version adding=20
DIME documents and correcting origin of documents.


Submission
Date:		<tbd>, 2007

From: 		IETF Working groups TSVWG, NSIS, DIME, SIP and SIPPING

To:		Georges Sebek  <tsbsg13@itu.int> ,
		Keith Knightson <kgk@igs.net>

Cc:		Magnus Westerlund <magnus.westerlund@ericsson.com>,
Lars Eggert <lars.eggert@nokia.com>,
James Polk <jmpolk@cisco.com>,
Martin Stiemerling <stiemerling@netlab.nec.de>,
John Loughney <john.loughney@nokia.com>
Dean Willis <dean.willis@softarmor.com>,
Keith Drage <drage@alcatel-lucent.com>,
Mary Barnes <mary.barnes@nortel.com>,
Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>,
Scott Bradner <sob@harvard.edu>,
Kimberly King <ksking@mitre.org>,
Scott Brim <swb@employees.org>,
Hannes Tschofenig <Hannes.Tschofenig@gmx.net>,
David Frascone <dave@frascone.com>

Response
Contact:	TSV WG (tsv-chairs@tools.ietf.org)
		NSIS (nsis-chairs@tools.ietf.org)
		SIPPING (sipping-chairs@tools.ietf.org)
		SIP (sip-chairs@tools.ietf.org)
		DIME (dime-chairs@tools.ietf.org)
	=09
Purpose: 	Response to Liaison Request

Deadline:	None

Title: Response to liaison request from ITU-T Study Group 13 work on=20
emergency telecommunications

This is a response to the liaison request made by Q.3/13 regarding=20
emergency telecommunications (REF: NGN-GSI/DOC =96 60 Rev.2). We would=20
first like to apologize for failing to meet the deadline in responding.=20
We do hope that the late answer still can be of some use.

The liaison request was made to the following working groups (WG):=20
IEPREP, TSVWG, and NSIS. Since the request was sent the IEPREP WG has=20
concluded. In addition to the WGs from which information was requested,=20
we also think that work performed by the DIME, SIP and SIPPING WG may be=20
of relevance.

Pursuant to ITU-T Study Group 13 request for information on relevant and=20
related work in the IETF regarding emergency communications, we list=20
below RFCs and works in progress that we feel may be of interest to your=20
group.  Some of the completed work is Informational, and others are in=20
the category of Standards Track.

Q.3/13 also requested that we keep you informed of any developments in=20
regards to emergency telecommunications. In those regards we would like=20
to make you aware that IETF mailing list participation and document=20
information is free and open to anyone, allowing participants in Q.3/13=20
to keep themselves informed of any developments. If Q.3/13 desire to get=20
further information about specific ongoing work, then please send a=20
liaison request to the responsible WG for those specific documents.

The following list is divided under the associated working groups from=20
which the work has been done within the IETF.


SIP Working Group

RFC 4412

Title:
    Communications Resource Priority for the Session Initiation
    Protocol (SIP)

Abstract:
    This document defines two new Session Initiation Protocol (SIP)
    header fields for communicating resource priority, namely,
    "Resource-Priority" and "Accept-Resource-Priority".  The
    "Resource-Priority" header field can influence the behavior of SIP
    user agents (such as telephone gateways and IP telephones) and SIP
    proxies.  It does not directly influence the forwarding behavior of
    IP routers.

	The below two documents are proposed work items accepted to become IETF=20
WG items are likely of interest as they update RFC 4412.

Work In Progress:   draft-polk-sip-rph-in-responses-00

Title:
Allowing SIP Resource Priority Header in SIP Responses

Abstract:
    The Session Initiation Protocol (SIP) Resource Priority Header
    (RPH), in its current form, is ignored in SIP responses.  This was a
    design choice during RFC 4412's development. This is now considered
    a bad design choice in certain scenarios.  This document corrects
    RFC 4412's communications model by optionally allowing a SIP server
    or user agent client to process the Resource-Priority Header in a
    response.

Work In Progress:   draft-polk-sip-rph-new-namespaces--00

Title:
New Session Initiation Protocol Resource-Priority Header Namespaces for=20
the Defense Information Systems Agency

Abstract:
    This document creates additional Session Initiation Protocol
    Resource-Priority header namespaces, to be IANA registered.  This
    document intends to update RFC 4412, as a Proposed Standard document
    if published by the RFC-Editor.



SIPPING Working Group

RFC 4411

Title:
    Extending the Session Initiation Protocol (SIP)
    Reason Header for Preemption Events

Abstract:
   This document proposes an IANA Registration extension to the Session
    Initiation Protocol (SIP) Reason Header to be included in a BYE
    Method Request as a result of a session preemption event, either at a
    user agent (UA), or somewhere in the network involving a
    reservation-based protocol such as the Resource ReSerVation Protocol
    (RSVP) or Next Steps in Signaling (NSIS).  This document does not
    attempt to address routers failing in the packet path; instead, it
    addresses a deliberate tear down of a flow between UAs, and informs
    the terminated UA(s) with an indication of what occurred.

IEPREP Working Group

RFC 3487

Title:
    Requirements for Resource Priority Mechanisms for the
    Session Initiation Protocol (SIP)

Abstract:
    This document summarizes requirements for prioritizing access to
    circuit-switched network, end system and proxy resources for
    emergency preparedness communications using the Session Initiation
    Protocol (SIP).

RFC 3689

Title:
    General Requirements for
    Emergency Telecommunication Service (ETS)

Abstract:
    This document presents a list of general requirements in support of
    Emergency Telecommunications Service (ETS).  Solutions to these
    requirements are not presented in this document.  Additional
    requirements pertaining to specific applications, or types of
    applications, are to be specified in separate document(s).

RFC 3690

Title:
    IP Telephony Requirements for
    Emergency Telecommunication Service (ETS)

Abstract:
    This document presents a list of requirements in support of Emergency
    Telecommunications Service (ETS) within the context of IP telephony.
    It is an extension to the general requirements presented in RFC 3689.
    Solutions to these requirements are not presented in this document.

RFC 4190

Title:
    Framework for Supporting Emergency Telecommunications
    Service (ETS) in IP Telephony

Abstract:
    This document presents a framework for supporting authorized,
    emergency-related communication within the context of IP telephony.
    We present a series of objectives that reflect a general view of how
    authorized emergency service, in line with the Emergency
    Telecommunications Service (ETS), should be realized within today's
    IP architecture and service models.  From these objectives, we
    present a corresponding set of protocols and capabilities, which
    provide a more specific set of recommendations regarding existing
    IETF protocols.  Finally, we present two scenarios that act as
    guiding models for the objectives and functions listed in this
    document.  These models, coupled with an example of an existing
    service in the Public Switched Telephone Network (PSTN), contribute
    to a constrained solution space.

RFC 4375

Title:
    Emergency Telecommunications Services (ETS) Requirements
    for a Single Administrative Domain

Abstract:
    This document presents a list of requirements in support of Emergency
    Telecommunications Service (ETS) within a single administrative
    domain.  This document focuses on a specific set of administrative
    constraints and scope.  Solutions to these requirements are not
    presented in this document.


TSV Working Group

RFC 4542

Title:
    Implementing an Emergency Telecommunications Service (ETS)
    for Real-Time Services in the Internet Protocol Suite

Abstract:
    RFCs 3689 and 3690 detail requirements for an Emergency
    Telecommunications Service (ETS), of which an Internet Emergency
    Preparedness Service (IEPS) would be a part.  Some of these types of
    services require call preemption; others require call queuing or
    other mechanisms.  IEPS requires a Call Admission Control (CAC)
    procedure and a Per Hop Behavior (PHB) for the data that meet the
    needs of this architecture.  Such a CAC procedure and PHB is
    appropriate to any service that might use H.323 or SIP to set up
    real-time sessions.  The key requirement is to guarantee an elevated
    probability of call completion to an authorized user in time of
    crisis.

    This document primarily discusses supporting ETS in the context of
    the US Government and NATO, because it focuses on the Multi-Level
    Precedence and Preemption (MLPP) and Government Emergency
    Telecommunication Service (GETS) standards.  The architectures
    described here are applicable beyond these organizations.

Work In Progress:   draft-ietf-tsvwg-emergency-rsvp-03.txt

Title:
    Resource ReSerVation Protovol (RSVP) Extensions for
    Emergency Services

Abstract:
    An Emergency Telecommunications Service (ETS) requires the ability to
    provide an elevated probability of session establishment to an
    authorized user in times of network congestion (typically, during a
    crisis). When supported over the Internet Protocol suite, this may be
    facilitated through a network layer admission control solution, which
    supports prioritized access to resources (e.g., bandwidth). These
    resources may be explicitly set aside for emergency services, or they
    may be shared with other sessions.

   This document specifies RSVP extensions that can be used to support
    such an admission priority capability at the network layer. Note that
    these extensions represent one possible solution component in
    satisfying ETS requirements. Other solution components, or other
    solutions, are outside the scope of this document.

NSIS Working Group

Work In Progress: draft-ietf-nsis-qos-nslp-14.txt

Title:
NSLP for Quality-of-Service Signaling

Abstract:
This specification describes the NSIS Signaling Layer Protocol (NSLP)=20
for signaling QoS reservations in the Internet.  It is in accordance=20
with the framework and requirements developed in NSIS.  Together with=20
GIST, it provides functionality similar to RSVP and extends it.  The QoS=20
NSLP is independent of the underlying QoS specification or architecture=20
and provides support for different reservation models. It is simplified=20
by the elimination of support for multicast flows. This specification=20
explains the overall protocol approach, design decisions made and=20
provides examples.  It specifies object, message  formats and processing=20
rules.

DIME Working Group

Work In Progress: draft-ietf-dime-diameter-qos-01.txt

Title:
   Diameter Quality of Service Application

Abstract:
   This document describes a Diameter application that performs
   Authentication, Authorization, and Accounting for Quality of Service
   (QoS) reservations.  This protocol is used by elements along the path
   of a given application flow to authenticate a reservation request,
   ensure that the reservation is authorized, and to account for
   resources consumed during the lifetime of the application flow.
   Clients that implement the Diameter QoS application contact an
   authorizing entity/application server that is located somewhere in
   the network, allowing for a wide variety of flexible deployment
   models.

Work In Progress: draft-ietf-dime-qos-parameters-00.txt

Title:
   Quality of Service Parameters for Usage with the AAA Framework

Abstract:
   This document defines a number of Quality of Service (QoS) parameters
   that can be reused for conveying QoS information within RADIUS and
   Diameter.

   The payloads used to carry these QoS parameters are opaque for the
   AAA client and the AAA server itself and interpreted by the
   respective Resource Management Function.

Work In Progress: draft-ietf-dime-qos-attributes-01.txt

Title:
   Quality of Service Attributes for Diameter and RADIUS

Abstract:
   This document extends the functionality of the Diameter Base protocol
   and other Diameter applications with respect to their ability to
   convey Quality of Service information.  The AVPs defined in this
   document are also available for Remote Authentication Dial In User
   Service (RADIUS).


Non-WG Documents

	Approved for publication: draft-carlberg-trip-attribute-rp-02.txt

	Title:
	  TRIP Attribute for Resource Priority
=09
Abstract:
    This document defines a new attribute for  the  TRIP  protocol.   The
    attribute   associates   protocols/services   in  the  PSTN  offering
    authorized  prioritization  during  call  setup  that  are  reachable
    through  a TRIP gateway.  Current examples of preferential service in
    the PSTN are Government Emergency Telecommunications  Service  (GETS)
    in  the U.S. and Government Telephone Preference Scheme (GTPS) in the
    U.K.  The proposed attribute for TRIP is based on the NameSpace.Value
    tupple defined for the SIP resource Priority field.




Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis





From tsvwg-bounces@ietf.org Tue Aug 28 03:57:41 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPvvV-0005rt-5W; Tue, 28 Aug 2007 03:55:53 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IPvvR-0005oU-Bd
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 28 Aug 2007 03:55:49 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPvvQ-0005nY-97; Tue, 28 Aug 2007 03:55:48 -0400
Received: from ccsmtpgate.mugla.edu.tr ([194.27.32.25]
	helo=ccsmtpgate.mu.edu.tr)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IPvvO-0000NA-SI; Tue, 28 Aug 2007 03:55:48 -0400
Received: from ccexc01.mu.edu.tr ([10.1.1.15]) by ccsmtpgate.mu.edu.tr with
	Microsoft SMTPSVC(6.0.3790.3959); Tue, 28 Aug 2007 11:01:49 +0300
Received: from mail pickup service by ccexc01.mu.edu.tr with Microsoft SMTPSVC;
	Tue, 28 Aug 2007 11:01:46 +0300
Received: from megatron.ietf.org ([156.154.16.145]) by ccsmtpgate.mu.edu.tr
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 27 Aug 2007 18:11:28 +0300
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPg9F-0007ci-8J; Mon, 27 Aug 2007 11:05:01 -0400
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1IPg9B-0007Yn-Eq
	for nsis-confirm+ok@megatron.ietf.org; Mon, 27 Aug 2007 11:04:57 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPg99-0007X2-UV; Mon, 27 Aug 2007 11:04:56 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IPg98-00077c-Eg; Mon, 27 Aug 2007 11:04:55 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	C8653207B1; Mon, 27 Aug 2007 17:04:47 +0200 (CEST)
X-AuditID: c1b4fb3c-b1e82bb0000007e1-c3-46d2e80fde06
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9C94C20671; Mon, 27 Aug 2007 17:04:47 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Aug 2007 17:04:46 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Aug 2007 17:04:46 +0200
Message-ID: <46D2E80E.8000001@ericsson.com>
Date: Mon, 27 Aug 2007 17:04:46 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <46AF5370.9020304@ericsson.com>
In-Reply-To: <46AF5370.9020304@ericsson.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
X-OriginalArrivalTime: 27 Aug 2007 15:04:46.0546 (UTC)
	FILETIME=[9B4E0B20:01C7E8BB]
X-Brightmail-Tracker: AAAAAA==
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9f79b8e383fd3af2b1b5b1d0910f6094
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 142a000676f5977e1797396caab8b611
Cc: sip@ietf.org, IETF SIPPING WG <sipping@ietf.org>, tsvwg <tsvwg@ietf.org>,
	NSIS <nsis@ietf.org>
Subject: [Tsvwg] [NSIS] Re: Draft Liaison response to SG13 on Emergency
	Telecommunications
X-BeenThere: tsvwg@ietf.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Hi,

I have now updated this liaison reply to take the comments into account.=20
According to the ECRIT chairs they don't think what they are working is=20
related to the ongoing work Q.3/13 is working on. If you have any final=20
comments please provide them no later then the Wednesday 29th at 16.00 CE=
ST.

Magnus Westerlund


Submission
Date:		<tbd>, 2007

From: 		IETF Working groups TSVWG, NSIS, SIP and SIPPING

To:		Georges Sebek  <tsbsg13@itu.int> ,
		Keith Knightson <kgk@igs.net>

Cc:		Magnus Westerlund <magnus.westerlund@ericsson.com>,
                 Lars Eggert <lars.eggert@nokia.com>,
                 James Polk <jmpolk@cisco.com>,
                 Martin Stiemerling <stiemerling@netlab.nec.de>,
                 John Loughney <john.loughney@nokia.com>
                 Dean Willis <dean.willis@softarmor.com>,
                 Keith Drage <drage@alcatel-lucent.com>,
                 Mary Barnes <mary.barnes@nortel.com>,
                 Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>,
                 Scott Bradner <sob@harvard.edu>,
                 Kimberly King <ksking@mitre.org>,
                 Scott Brim <swb@employees.org>

Response
Contact:	TSV WG (tsv-chairs@tools.ietf.org)
		NSIS (nsis-chairs@tools.ietf.org)
		SIPPING (sipping-chairs@tools.ietf.org)
		SIP (sip-chairs@tools.ietf.org)
	=09
Purpose: 	Response to Liaison Request

Deadline:	None

Title: Response to liaison request from ITU-T Study Group 13 work on=20
emergency telecommunications

This is a response to the liaison request made by Q.3/13 regarding=20
emergency telecommunications (REF: NGN-GSI/DOC =E2=80=93 60 Rev.2). We wo=
uld=20
first like to apologize for failing to meet the deadline in responding.=20
We do hope that the late answer still can be of some use.

The liaison request was made to the following working groups (WG):=20
IEPREP, TSVWG, and NSIS. Since the request was sent the IEPREP WG has=20
concluded. In addition to the WGs from which information was requested,=20
we also think that work performed by the SIP and SIPPING WG may be of=20
relevance.

Pursuant to ITU-T Study Group 13 request for information on relevant and=20
related work in the IETF regarding emergency communications, we list=20
below RFCs and works in progress that we feel may be of interest to your=20
group.  Some of the completed work is Informational, and others are in=20
the category of Standards Track.

Q.3/13 also requested that we keep you informed of any developments in=20
regards to emergency telecommunications. In those regards we would like=20
to make you aware that IETF mailing list participation and document=20
information is free and open to anyone, allowing participants in Q.3/13=20
to keep themselves informed of any developments. If Q.3/13 desire to get=20
further information about specific ongoing work, then please send a=20
liaison request to the responsible WG for those specific documents.

The following list is divided under the associated working groups from=20
which the work has been done within the IETF.


SIP Working Group

RFC 4411

Title:
    Extending the Session Initiation Protocol (SIP)
    Reason Header for Preemption Events

Abstract:
   This document proposes an IANA Registration extension to the Session
    Initiation Protocol (SIP) Reason Header to be included in a BYE
    Method Request as a result of a session preemption event, either at a
    user agent (UA), or somewhere in the network involving a
    reservation-based protocol such as the Resource ReSerVation Protocol
    (RSVP) or Next Steps in Signaling (NSIS).  This document does not
    attempt to address routers failing in the packet path; instead, it
    addresses a deliberate tear down of a flow between UAs, and informs
    the terminated UA(s) with an indication of what occurred.

RFC 4412

Title:
    Communications Resource Priority for the Session Initiation
    Protocol (SIP)

Abstract:
    This document defines two new Session Initiation Protocol (SIP)
    header fields for communicating resource priority, namely,
    "Resource-Priority" and "Accept-Resource-Priority".  The
    "Resource-Priority" header field can influence the behavior of SIP
    user agents (such as telephone gateways and IP telephones) and SIP
    proxies.  It does not directly influence the forwarding behavior of
    IP routers.



SIPPING Working Group

	The below two documents are proposed work items accepted to become IETF=20
WG items are likely of interest as they update RFC 4412.

Work In Progress:   draft-polk-sip-rph-in-responses-00

Title:
Allowing SIP Resource Priority Header in SIP Responses

Abstract:
    The Session Initiation Protocol (SIP) Resource Priority Header
    (RPH), in its current form, is ignored in SIP responses.  This was a
    design choice during RFC 4412's development. This is now considered
    a bad design choice in certain scenarios.  This document corrects
    RFC 4412's communications model by optionally allowing a SIP server
    or user agent client to process the Resource-Priority Header in a
    response.

Work In Progress:   draft-polk-sip-rph-new-namespaces--00

Title:
New Session Initiation Protocol Resource-Priority Header Namespaces for=20
the Defense Information Systems Agency

Abstract:
    This document creates additional Session Initiation Protocol
    Resource-Priority header namespaces, to be IANA registered.  This
    document intends to update RFC 4412, as a Proposed Standard document
    if published by the RFC-Editor.

IEPREP Working Group

RFC 3487

Title:
    Requirements for Resource Priority Mechanisms for the
    Session Initiation Protocol (SIP)

Abstract:
    This document summarizes requirements for prioritizing access to
    circuit-switched network, end system and proxy resources for
    emergency preparedness communications using the Session Initiation
    Protocol (SIP).

RFC 3689

Title:
    General Requirements for
    Emergency Telecommunication Service (ETS)

Abstract:
    This document presents a list of general requirements in support of
    Emergency Telecommunications Service (ETS).  Solutions to these
    requirements are not presented in this document.  Additional
    requirements pertaining to specific applications, or types of
    applications, are to be specified in separate document(s).

RFC 3690

Title:
    IP Telephony Requirements for
    Emergency Telecommunication Service (ETS)

Abstract:
    This document presents a list of requirements in support of Emergency
    Telecommunications Service (ETS) within the context of IP telephony.
    It is an extension to the general requirements presented in RFC 3689.
    Solutions to these requirements are not presented in this document.

RFC 4190

Title:
    Framework for Supporting Emergency Telecommunications
    Service (ETS) in IP Telephony

Abstract:
    This document presents a framework for supporting authorized,
    emergency-related communication within the context of IP telephony.
    We present a series of objectives that reflect a general view of how
    authorized emergency service, in line with the Emergency
    Telecommunications Service (ETS), should be realized within today's
    IP architecture and service models.  From these objectives, we
    present a corresponding set of protocols and capabilities, which
    provide a more specific set of recommendations regarding existing
    IETF protocols.  Finally, we present two scenarios that act as
    guiding models for the objectives and functions listed in this
    document.  These models, coupled with an example of an existing
    service in the Public Switched Telephone Network (PSTN), contribute
    to a constrained solution space.

RFC 4375

Title:
    Emergency Telecommunications Services (ETS) Requirements
    for a Single Administrative Domain

Abstract:
    This document presents a list of requirements in support of Emergency
    Telecommunications Service (ETS) within a single administrative
    domain.  This document focuses on a specific set of administrative
    constraints and scope.  Solutions to these requirements are not
    presented in this document.


TSV Working Group

RFC 4542

Title:
    Implementing an Emergency Telecommunications Service (ETS)
    for Real-Time Services in the Internet Protocol Suite

Abstract:
    RFCs 3689 and 3690 detail requirements for an Emergency
    Telecommunications Service (ETS), of which an Internet Emergency
    Preparedness Service (IEPS) would be a part.  Some of these types of
    services require call preemption; others require call queuing or
    other mechanisms.  IEPS requires a Call Admission Control (CAC)
    procedure and a Per Hop Behavior (PHB) for the data that meet the
    needs of this architecture.  Such a CAC procedure and PHB is
    appropriate to any service that might use H.323 or SIP to set up
    real-time sessions.  The key requirement is to guarantee an elevated
    probability of call completion to an authorized user in time of
    crisis.

    This document primarily discusses supporting ETS in the context of
    the US Government and NATO, because it focuses on the Multi-Level
    Precedence and Preemption (MLPP) and Government Emergency
    Telecommunication Service (GETS) standards.  The architectures
    described here are applicable beyond these organizations.

Work In Progress:   draft-ietf-tsvwg-emergency-rsvp-03.txt

Title:
    Resource ReSerVation Protovol (RSVP) Extensions for
    Emergency Services

Abstract:
    An Emergency Telecommunications Service (ETS) requires the ability to
    provide an elevated probability of session establishment to an
    authorized user in times of network congestion (typically, during a
    crisis). When supported over the Internet Protocol suite, this may be
    facilitated through a network layer admission control solution, which
    supports prioritized access to resources (e.g., bandwidth). These
    resources may be explicitly set aside for emergency services, or they
    may be shared with other sessions.

   This document specifies RSVP extensions that can be used to support
    such an admission priority capability at the network layer. Note that
    these extensions represent one possible solution component in
    satisfying ETS requirements. Other solution components, or other
    solutions, are outside the scope of this document.

NSIS Working Group

Work In Progress: draft-ietf-nsis-qos-nslp-14.txt

Title:
NSLP for Quality-of-Service Signaling

Abstract:
This specification describes the NSIS Signaling Layer Protocol (NSLP)=20
for signaling QoS reservations in the Internet.  It is in accordance=20
with the framework and requirements developed in NSIS.  Together with=20
GIST, it provides functionality similar to RSVP and extends it.  The QoS=20
NSLP is independent of the underlying QoS specification or architecture=20
and provides support for different reservation models. It is simplified=20
by the elimination of support for multicast flows. This specification=20
explains the overall protocol approach, design decisions made and=20
provides examples.  It specifies object, message  formats and processing=20
rules.

Non-WG Documents

	Approved for publication: draft-carlberg-trip-attribute-rp-02.txt

	Title:
	  TRIP Attribute for Resource Priority
=09
Abstract:
    This document defines a new attribute for  the  TRIP  protocol.   The
    attribute   associates   protocols/services   in  the  PSTN  offering
    authorized  prioritization  during  call  setup  that  are  reachable
    through  a TRIP gateway.  Current examples of preferential service in
    the PSTN are Government Emergency Telecommunications  Service  (GETS)
    in  the U.S. and Government Telephone Preference Scheme (GTPS) in the
    U.K.  The proposed attribute for TRIP is based on the NameSpace.Value
    tupple defined for the SIP resource Priority field.



--=20

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis





From tsvwg-bounces@ietf.org Tue Aug 28 03:57:49 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPvvj-0006aP-RQ; Tue, 28 Aug 2007 03:56:07 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IPvvT-0005qn-Ot
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 28 Aug 2007 03:55:51 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPvvS-0005pK-KJ; Tue, 28 Aug 2007 03:55:50 -0400
Received: from ccsmtpgate.mugla.edu.tr ([194.27.32.25]
	helo=ccsmtpgate.mu.edu.tr)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IPvvR-0000NA-3x; Tue, 28 Aug 2007 03:55:50 -0400
Received: from ccexc01.mu.edu.tr ([10.1.1.15]) by ccsmtpgate.mu.edu.tr with
	Microsoft SMTPSVC(6.0.3790.3959); Tue, 28 Aug 2007 11:01:49 +0300
Received: from mail pickup service by ccexc01.mu.edu.tr with Microsoft SMTPSVC;
	Tue, 28 Aug 2007 11:01:46 +0300
Received: from megatron.ietf.org ([156.154.16.145]) by ccsmtpgate.mu.edu.tr
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 27 Aug 2007 20:50:36 +0300
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPidI-0002JZ-GW; Mon, 27 Aug 2007 13:44:12 -0400
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1IPidH-0002Iw-5y
	for nsis-confirm+ok@megatron.ietf.org; Mon, 27 Aug 2007 13:44:11 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPidG-0002Ii-Pa; Mon, 27 Aug 2007 13:44:10 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IPidF-0003fu-6e; Mon, 27 Aug 2007 13:44:10 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-4.cisco.com with ESMTP; 27 Aug 2007 10:44:08 -0700
X-IronPort-AV: i="4.19,312,1183359600"; d="scan'208"; a="8948966:sNHT37752318"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7RHi8I9018831; 
	Mon, 27 Aug 2007 10:44:08 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7RHi7lH024692;
	Mon, 27 Aug 2007 17:44:08 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Aug 2007 10:43:58 -0700
Received: from jmpolk-wxp.cisco.com ([10.21.91.203]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Aug 2007 10:43:58 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 27 Aug 2007 12:43:56 -0500
To: Magnus Westerlund <magnus.westerlund@ericsson.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <46D2E80E.8000001@ericsson.com>
References: <46AF5370.9020304@ericsson.com>
 <46D2E80E.8000001@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Message-ID: <XFE-SJC-211IFprhMOg0000051a@xfe-sjc-211.amer.cisco.com>
X-OriginalArrivalTime: 27 Aug 2007 17:43:58.0357 (UTC)
	FILETIME=[D8A0BC50:01C7E8D1]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=13773; t=1188236648;
	x=1189100648; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jmpolk@cisco.com;
	z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Re=3A=20Draft=20Liaison=20response=20to=20SG1
	3=20on=20Emergency=0A=20=20Telecommunications |Sender:=20;
	bh=sD60hnFy/1jeEK1NSSply5RPrbOwmB6enSRDS4sAZwA=;
	b=NJ5rCWq1ZGUUY+eJFusmZiG9HMDYbUGWMPHFX+snThPELoZWBHziyWTEWKUzwvNCia6c+Xib
	Su+2TerJMq4GI4YlehPPQ+olRzN0EU6a4fDGso7kncfj3xpvjujDn5RU;
Authentication-Results: sj-dkim-2; header.From=jmpolk@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8921dd2ebcb07edebf7bfaf4808c2ad
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 96e0f8497f38c15fbfc8f6f315bcdecb
Cc: sip@ietf.org, IETF SIPPING WG <sipping@ietf.org>, tsvwg <tsvwg@ietf.org>,
	NSIS <nsis@ietf.org>
Subject: [Tsvwg] [NSIS] Re: [Sip] Re: Draft Liaison response to SG13 on
 Emergency Telecommunications
X-BeenThere: tsvwg@ietf.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Magnus

comments in-line below about from which WG certain documents originated

At 10:04 AM 8/27/2007, Magnus Westerlund wrote:
>Hi,
>
>I have now updated this liaison reply to take=20
>the comments into account. According to the=20
>ECRIT chairs they don't think what they are=20
>working is related to the ongoing work Q.3/13 is=20
>working on. If you have any final comments=20
>please provide them no later then the Wednesday 29th at 16.00 CEST.
>
>Magnus Westerlund
>
>
>Submission
>Date:           <tbd>, 2007
>
>From:           IETF Working groups TSVWG, NSIS, SIP and SIPPING
>
>To:             Georges Sebek  <tsbsg13@itu.int> ,
>                 Keith Knightson <kgk@igs.net>
>
>Cc:             Magnus Westerlund <magnus.westerlund@ericsson.com>,
>                 Lars Eggert <lars.eggert@nokia.com>,
>                 James Polk <jmpolk@cisco.com>,
>                 Martin Stiemerling <stiemerling@netlab.nec.de>,
>                 John Loughney <john.loughney@nokia.com>
>                 Dean Willis <dean.willis@softarmor.com>,
>                 Keith Drage <drage@alcatel-lucent.com>,
>                 Mary Barnes <mary.barnes@nortel.com>,
>                 Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>,
>                 Scott Bradner <sob@harvard.edu>,
>                 Kimberly King <ksking@mitre.org>,
>                 Scott Brim <swb@employees.org>
>
>Response
>Contact:        TSV WG (tsv-chairs@tools.ietf.org)
>                 NSIS (nsis-chairs@tools.ietf.org)
>                 SIPPING (sipping-chairs@tools.ietf.org)
>                 SIP (sip-chairs@tools.ietf.org)
>
>Purpose:        Response to Liaison Request
>
>Deadline:       None
>
>Title: Response to liaison request from ITU-T=20
>Study Group 13 work on emergency telecommunications
>
>This is a response to the liaison request made=20
>by Q.3/13 regarding emergency telecommunications=20
>(REF: NGN-GSI/DOC =AD 60 Rev.2). We woould first=20
>like to apologize for failing to meet the=20
>deadline in responding. We do hope that the late=20
>answer still can be of some use.
>
>The liaison request was made to the following=20
>working groups (WG): IEPREP, TSVWG, and NSIS.=20
>Since the request was sent the IEPREP WG has=20
>concluded. In addition to the WGs from which=20
>information was requested, we also think that=20
>work performed by the SIP and SIPPING WG may be of relevance.
>
>Pursuant to ITU-T Study Group 13 request for=20
>information on relevant and related work in the=20
>IETF regarding emergency communications, we list=20
>below RFCs and works in progress that we feel=20
>may be of interest to your group.  Some of the=20
>completed work is Informational, and others are=20
>in the category of Standards Track.
>
>Q.3/13 also requested that we keep you informed=20
>of any developments in regards to emergency=20
>telecommunications. In those regards we would=20
>like to make you aware that IETF mailing list=20
>participation and document information is free=20
>and open to anyone, allowing participants in=20
>Q.3/13 to keep themselves informed of any=20
>developments. If Q.3/13 desire to get further=20
>information about specific ongoing work, then=20
>please send a liaison request to the responsible=20
>WG for those specific documents.
>
>The following list is divided under the=20
>associated working groups from which the work has been done within the=
 IETF.
>
>
>SIP Working Group
>
>RFC 4411

RFC4411 is from SIPPING


>Title:
>    Extending the Session Initiation Protocol (SIP)
>    Reason Header for Preemption Events
>
>Abstract:
>   This document proposes an IANA Registration extension to the Session
>    Initiation Protocol (SIP) Reason Header to be included in a BYE
>    Method Request as a result of a session preemption event, either at a
>    user agent (UA), or somewhere in the network involving a
>    reservation-based protocol such as the Resource ReSerVation Protocol
>    (RSVP) or Next Steps in Signaling (NSIS).  This document does not
>    attempt to address routers failing in the packet path; instead, it
>    addresses a deliberate tear down of a flow between UAs, and informs
>    the terminated UA(s) with an indication of what occurred.
>
>RFC 4412
>
>Title:
>    Communications Resource Priority for the Session Initiation
>    Protocol (SIP)
>
>Abstract:
>    This document defines two new Session Initiation Protocol (SIP)
>    header fields for communicating resource priority, namely,
>    "Resource-Priority" and "Accept-Resource-Priority".  The
>    "Resource-Priority" header field can influence the behavior of SIP
>    user agents (such as telephone gateways and IP telephones) and SIP
>    proxies.  It does not directly influence the forwarding behavior of
>    IP routers.
>
>
>
>SIPPING Working Group

both IDs below are SIP WG items, not SIPPING


>         The below two documents are proposed=20
> work items accepted to become IETF WG items are=20
> likely of interest as they update RFC 4412.
>
>Work In Progress:   draft-polk-sip-rph-in-responses-00
>
>Title:
>Allowing SIP Resource Priority Header in SIP Responses
>
>Abstract:
>    The Session Initiation Protocol (SIP) Resource Priority Header
>    (RPH), in its current form, is ignored in SIP responses.  This was a
>    design choice during RFC 4412's development. This is now considered
>    a bad design choice in certain scenarios.  This document corrects
>    RFC 4412's communications model by optionally allowing a SIP server
>    or user agent client to process the Resource-Priority Header in a
>    response.
>
>Work In Progress:   draft-polk-sip-rph-new-namespaces--00
>
>Title:
>New Session Initiation Protocol=20
>Resource-Priority Header Namespaces for the Defense Information Systems=
 Agency
>
>Abstract:
>    This document creates additional Session Initiation Protocol
>    Resource-Priority header namespaces, to be IANA registered.  This
>    document intends to update RFC 4412, as a Proposed Standard document
>    if published by the RFC-Editor.
>
>IEPREP Working Group
>
>RFC 3487
>
>Title:
>    Requirements for Resource Priority Mechanisms for the
>    Session Initiation Protocol (SIP)
>
>Abstract:
>    This document summarizes requirements for prioritizing access to
>    circuit-switched network, end system and proxy resources for
>    emergency preparedness communications using the Session Initiation
>    Protocol (SIP).
>
>RFC 3689
>
>Title:
>    General Requirements for
>    Emergency Telecommunication Service (ETS)
>
>Abstract:
>    This document presents a list of general requirements in support of
>    Emergency Telecommunications Service (ETS).  Solutions to these
>    requirements are not presented in this document.  Additional
>    requirements pertaining to specific applications, or types of
>    applications, are to be specified in separate document(s).
>
>RFC 3690
>
>Title:
>    IP Telephony Requirements for
>    Emergency Telecommunication Service (ETS)
>
>Abstract:
>    This document presents a list of requirements in support of Emergency
>    Telecommunications Service (ETS) within the context of IP telephony.
>    It is an extension to the general requirements presented in RFC 3689.
>    Solutions to these requirements are not presented in this document.
>
>RFC 4190
>
>Title:
>    Framework for Supporting Emergency Telecommunications
>    Service (ETS) in IP Telephony
>
>Abstract:
>    This document presents a framework for supporting authorized,
>    emergency-related communication within the context of IP telephony.
>    We present a series of objectives that reflect a general view of how
>    authorized emergency service, in line with the Emergency
>    Telecommunications Service (ETS), should be realized within today's
>    IP architecture and service models.  From these objectives, we
>    present a corresponding set of protocols and capabilities, which
>    provide a more specific set of recommendations regarding existing
>    IETF protocols.  Finally, we present two scenarios that act as
>    guiding models for the objectives and functions listed in this
>    document.  These models, coupled with an example of an existing
>    service in the Public Switched Telephone Network (PSTN), contribute
>    to a constrained solution space.
>
>RFC 4375
>
>Title:
>    Emergency Telecommunications Services (ETS) Requirements
>    for a Single Administrative Domain
>
>Abstract:
>    This document presents a list of requirements in support of Emergency
>    Telecommunications Service (ETS) within a single administrative
>    domain.  This document focuses on a specific set of administrative
>    constraints and scope.  Solutions to these requirements are not
>    presented in this document.
>
>
>TSV Working Group
>
>RFC 4542
>
>Title:
>    Implementing an Emergency Telecommunications Service (ETS)
>    for Real-Time Services in the Internet Protocol Suite
>
>Abstract:
>    RFCs 3689 and 3690 detail requirements for an Emergency
>    Telecommunications Service (ETS), of which an Internet Emergency
>    Preparedness Service (IEPS) would be a part.  Some of these types of
>    services require call preemption; others require call queuing or
>    other mechanisms.  IEPS requires a Call Admission Control (CAC)
>    procedure and a Per Hop Behavior (PHB) for the data that meet the
>    needs of this architecture.  Such a CAC procedure and PHB is
>    appropriate to any service that might use H.323 or SIP to set up
>    real-time sessions.  The key requirement is to guarantee an elevated
>    probability of call completion to an authorized user in time of
>    crisis.
>
>    This document primarily discusses supporting ETS in the context of
>    the US Government and NATO, because it focuses on the Multi-Level
>    Precedence and Preemption (MLPP) and Government Emergency
>    Telecommunication Service (GETS) standards.  The architectures
>    described here are applicable beyond these organizations.
>
>Work In Progress:   draft-ietf-tsvwg-emergency-rsvp-03.txt
>
>Title:
>    Resource ReSerVation Protovol (RSVP) Extensions for
>    Emergency Services
>
>Abstract:
>    An Emergency Telecommunications Service (ETS) requires the ability to
>    provide an elevated probability of session establishment to an
>    authorized user in times of network congestion (typically, during a
>    crisis). When supported over the Internet Protocol suite, this may be
>    facilitated through a network layer admission control solution, which
>    supports prioritized access to resources (e.g., bandwidth). These
>    resources may be explicitly set aside for emergency services, or they
>    may be shared with other sessions.
>
>   This document specifies RSVP extensions that can be used to support
>    such an admission priority capability at the network layer. Note that
>    these extensions represent one possible solution component in
>    satisfying ETS requirements. Other solution components, or other
>    solutions, are outside the scope of this document.
>
>NSIS Working Group
>
>Work In Progress: draft-ietf-nsis-qos-nslp-14.txt
>
>Title:
>NSLP for Quality-of-Service Signaling
>
>Abstract:
>This specification describes the NSIS Signaling=20
>Layer Protocol (NSLP) for signaling QoS=20
>reservations in the Internet.  It is in=20
>accordance with the framework and requirements=20
>developed in NSIS.  Together with GIST, it=20
>provides functionality similar to RSVP and=20
>extends it.  The QoS NSLP is independent of the=20
>underlying QoS specification or architecture and=20
>provides support for different reservation=20
>models. It is simplified by the elimination of=20
>support for multicast flows. This specification=20
>explains the overall protocol approach, design=20
>decisions made and provides examples.  It=20
>specifies object, message  formats and processing rules.
>
>Non-WG Documents
>
>         Approved for publication: draft-carlberg-trip-attribute-rp-02.txt
>
>         Title:
>           TRIP Attribute for Resource Priority
>
>Abstract:
>    This document defines a new attribute for  the  TRIP  protocol.   The
>    attribute   associates   protocols/services   in  the  PSTN  offering
>    authorized  prioritization  during  call  setup  that  are  reachable
>    through  a TRIP gateway.  Current examples of preferential service in
>    the PSTN are Government Emergency Telecommunications  Service  (GETS)
>    in  the U.S. and Government Telephone Preference Scheme (GTPS) in the
>    U.K.  The proposed attribute for TRIP is based on the NameSpace.Value
>    tupple defined for the SIP resource Priority field.
>
>
>
>--
>
>Magnus Westerlund
>
>IETF Transport Area Director & TSVWG Chair
>----------------------------------------------------------------------
>Multimedia Technologies, Ericsson Research EAB/TVM/M
>----------------------------------------------------------------------
>Ericsson AB                | Phone +46 8 4048287
>Torshamsgatan 23           | Fax   +46 8 7575550
>S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>----------------------------------------------------------------------
>
>
>_______________________________________________
>Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sipping@ietf.org for new developments on the application of sip


_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis





From tsvwg-bounces@ietf.org Tue Aug 28 07:09:20 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPyuy-00020G-Ru; Tue, 28 Aug 2007 07:07:32 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IPyux-00020B-SH
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 28 Aug 2007 07:07:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPyux-000203-Hu
	for tsvwg@ietf.org; Tue, 28 Aug 2007 07:07:31 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPyux-0004RU-3c
	for tsvwg@ietf.org; Tue, 28 Aug 2007 07:07:31 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	307C920752
	for <tsvwg@ietf.org>; Tue, 28 Aug 2007 13:07:30 +0200 (CEST)
X-AuditID: c1b4fb3c-b1681bb0000007e1-13-46d401f2f139
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	239F220710
	for <tsvwg@ietf.org>; Tue, 28 Aug 2007 13:07:30 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Aug 2007 13:07:29 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Aug 2007 13:07:29 +0200
Message-ID: <46D401F1.8050407@ericsson.com>
Date: Tue, 28 Aug 2007 13:07:29 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Aug 2007 11:07:29.0813 (UTC)
	FILETIME=[9FF6BC50:01C7E963]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [Tsvwg] Working group last call:
	draft-ietf-tsvwg-diffserv-class-aggr-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

This announces a 2 week working group last call on "Aggregation of
DiffServ Service Classes" (draft-ietf-tsvwg-diffserv-class-aggr-04) for
publication as an informational RFC. Please provide any feedback no
later than Tuesday the 11th of September.

http://tools.ietf.org/html/draft-ietf-tsvwg-diffserv-class-aggr-04

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------





From tsvwg-bounces@ietf.org Tue Aug 28 14:01:25 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQ5Lj-0004xU-4c; Tue, 28 Aug 2007 13:59:35 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IQ5Lh-0004wx-0i
	for tsvwg-confirm+ok@megatron.ietf.org; Tue, 28 Aug 2007 13:59:33 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQ5Lg-0004wc-Ac; Tue, 28 Aug 2007 13:59:32 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IQ5Le-0000b0-OY; Tue, 28 Aug 2007 13:59:32 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-1.cisco.com with ESMTP; 28 Aug 2007 10:59:29 -0700
X-IronPort-AV: i="4.19,317,1183359600"; 
	d="scan'208"; a="15348078:sNHT40240212"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l7SHxTN2013270; 
	Tue, 28 Aug 2007 10:59:29 -0700
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 l7SHxClh008831;
	Tue, 28 Aug 2007 17:59:29 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Aug 2007 10:59:21 -0700
Received: from jmpolk-wxp.cisco.com ([10.21.123.166]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Aug 2007 10:59:21 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 28 Aug 2007 12:59:22 -0500
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [NSIS] Re: [Tsvwg] Re: [Sip] Re: Draft Liaison response to
	SG13 on Emergency Telecommunications
In-Reply-To: <46D3CFCF.6070308@ericsson.com>
References: <46AF5370.9020304@ericsson.com> <46D2E80E.8000001@ericsson.com>
	<XFE-SJC-211IFprhMOg0000051a@xfe-sjc-211.amer.cisco.com>
	<46D3CFCF.6070308@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Message-ID: <XFE-SJC-211H71yEXUI000006c7@xfe-sjc-211.amer.cisco.com>
X-OriginalArrivalTime: 28 Aug 2007 17:59:21.0205 (UTC)
	FILETIME=[2919EA50:01C7E99D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=14975; t=1188323969;
	x=1189187969; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jmpolk@cisco.com;
	z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com>
	|Subject:=20Re=3A=20[NSIS]=20Re=3A=20[Tsvwg]=20Re=3A=20[Sip]=20Re=3A=20Dr
	aft=20Liaison=20response=20to=0A=20=20SG13=20on=20Emergency=20Telecommunic
	ations |Sender:=20;
	bh=m99wFMraDniP/oabHCb59sGhsw2Bm5NRjjTI8QPmPjQ=;
	b=bODCQI96h2iutBG4vGsYcbj1e/Oo4s0WfBpHF2E8WSTSIdETsS+MhpFOBid8YxpSICPCI97d
	sdgboM6xqHbePJ1KuM3XLQaNN2jxktMXOXQIgqArKt8G+EV6TaxcEWe+;
Authentication-Results: sj-dkim-3; header.From=jmpolk@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 89ebdf268eceaeaf784b3acb625dc20e
Cc: sip@ietf.org, IETF SIPPING WG <sipping@ietf.org>, dime@ietf.org,
	tsvwg <tsvwg@ietf.org>, NSIS <nsis@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

this is good with me

At 02:33 AM 8/28/2007, Magnus Westerlund wrote:
>Hi again,
>
>I have received some more comments. So here is=20
>an updated version adding DIME documents and correcting origin of=
 documents.
>
>
>Submission
>Date:           <tbd>, 2007
>
>From:           IETF Working groups TSVWG, NSIS, DIME, SIP and SIPPING
>
>To:             Georges Sebek  <tsbsg13@itu.int> ,
>                 Keith Knightson <kgk@igs.net>
>
>Cc:             Magnus Westerlund <magnus.westerlund@ericsson.com>,
>Lars Eggert <lars.eggert@nokia.com>,
>James Polk <jmpolk@cisco.com>,
>Martin Stiemerling <stiemerling@netlab.nec.de>,
>John Loughney <john.loughney@nokia.com>
>Dean Willis <dean.willis@softarmor.com>,
>Keith Drage <drage@alcatel-lucent.com>,
>Mary Barnes <mary.barnes@nortel.com>,
>Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>,
>Scott Bradner <sob@harvard.edu>,
>Kimberly King <ksking@mitre.org>,
>Scott Brim <swb@employees.org>,
>Hannes Tschofenig <Hannes.Tschofenig@gmx.net>,
>David Frascone <dave@frascone.com>
>
>Response
>Contact:        TSV WG (tsv-chairs@tools.ietf.org)
>                 NSIS (nsis-chairs@tools.ietf.org)
>                 SIPPING (sipping-chairs@tools.ietf.org)
>                 SIP (sip-chairs@tools.ietf.org)
>                 DIME (dime-chairs@tools.ietf.org)
>
>Purpose:        Response to Liaison Request
>
>Deadline:       None
>
>Title: Response to liaison request from ITU-T=20
>Study Group 13 work on emergency telecommunications
>
>This is a response to the liaison request made=20
>by Q.3/13 regarding emergency telecommunications=20
>(REF: NGN-GSI/DOC =AD 60 Rev.2). We would first=20
>like to apologize for failing to meet the=20
>deadline in responding. We do hope that the late=20
>answer still can be of some use.
>
>The liaison request was made to the following=20
>working groups (WG): IEPREP, TSVWG, and NSIS.=20
>Since the request was sent the IEPREP WG has=20
>concluded. In addition to the WGs from which=20
>information was requested, we also think that=20
>work performed by the DIME, SIP and SIPPING WG may be of relevance.
>
>Pursuant to ITU-T Study Group 13 request for=20
>information on relevant and related work in the=20
>IETF regarding emergency communications, we list=20
>below RFCs and works in progress that we feel=20
>may be of interest to your group.  Some of the=20
>completed work is Informational, and others are=20
>in the category of Standards Track.
>
>Q.3/13 also requested that we keep you informed=20
>of any developments in regards to emergency=20
>telecommunications. In those regards we would=20
>like to make you aware that IETF mailing list=20
>participation and document information is free=20
>and open to anyone, allowing participants in=20
>Q.3/13 to keep themselves informed of any=20
>developments. If Q.3/13 desire to get further=20
>information about specific ongoing work, then=20
>please send a liaison request to the responsible=20
>WG for those specific documents.
>
>The following list is divided under the=20
>associated working groups from which the work has been done within the=
 IETF.
>
>
>SIP Working Group
>
>RFC 4412
>
>Title:
>    Communications Resource Priority for the Session Initiation
>    Protocol (SIP)
>
>Abstract:
>    This document defines two new Session Initiation Protocol (SIP)
>    header fields for communicating resource priority, namely,
>    "Resource-Priority" and "Accept-Resource-Priority".  The
>    "Resource-Priority" header field can influence the behavior of SIP
>    user agents (such as telephone gateways and IP telephones) and SIP
>    proxies.  It does not directly influence the forwarding behavior of
>    IP routers.
>
>         The below two documents are proposed=20
> work items accepted to become IETF WG items are=20
> likely of interest as they update RFC 4412.
>
>Work In Progress:   draft-polk-sip-rph-in-responses-00
>
>Title:
>Allowing SIP Resource Priority Header in SIP Responses
>
>Abstract:
>    The Session Initiation Protocol (SIP) Resource Priority Header
>    (RPH), in its current form, is ignored in SIP responses.  This was a
>    design choice during RFC 4412's development. This is now considered
>    a bad design choice in certain scenarios.  This document corrects
>    RFC 4412's communications model by optionally allowing a SIP server
>    or user agent client to process the Resource-Priority Header in a
>    response.
>
>Work In Progress:   draft-polk-sip-rph-new-namespaces--00
>
>Title:
>New Session Initiation Protocol=20
>Resource-Priority Header Namespaces for the Defense Information Systems=
 Agency
>
>Abstract:
>    This document creates additional Session Initiation Protocol
>    Resource-Priority header namespaces, to be IANA registered.  This
>    document intends to update RFC 4412, as a Proposed Standard document
>    if published by the RFC-Editor.
>
>
>
>SIPPING Working Group
>
>RFC 4411
>
>Title:
>    Extending the Session Initiation Protocol (SIP)
>    Reason Header for Preemption Events
>
>Abstract:
>   This document proposes an IANA Registration extension to the Session
>    Initiation Protocol (SIP) Reason Header to be included in a BYE
>    Method Request as a result of a session preemption event, either at a
>    user agent (UA), or somewhere in the network involving a
>    reservation-based protocol such as the Resource ReSerVation Protocol
>    (RSVP) or Next Steps in Signaling (NSIS).  This document does not
>    attempt to address routers failing in the packet path; instead, it
>    addresses a deliberate tear down of a flow between UAs, and informs
>    the terminated UA(s) with an indication of what occurred.
>
>IEPREP Working Group
>
>RFC 3487
>
>Title:
>    Requirements for Resource Priority Mechanisms for the
>    Session Initiation Protocol (SIP)
>
>Abstract:
>    This document summarizes requirements for prioritizing access to
>    circuit-switched network, end system and proxy resources for
>    emergency preparedness communications using the Session Initiation
>    Protocol (SIP).
>
>RFC 3689
>
>Title:
>    General Requirements for
>    Emergency Telecommunication Service (ETS)
>
>Abstract:
>    This document presents a list of general requirements in support of
>    Emergency Telecommunications Service (ETS).  Solutions to these
>    requirements are not presented in this document.  Additional
>    requirements pertaining to specific applications, or types of
>    applications, are to be specified in separate document(s).
>
>RFC 3690
>
>Title:
>    IP Telephony Requirements for
>    Emergency Telecommunication Service (ETS)
>
>Abstract:
>    This document presents a list of requirements in support of Emergency
>    Telecommunications Service (ETS) within the context of IP telephony.
>    It is an extension to the general requirements presented in RFC 3689.
>    Solutions to these requirements are not presented in this document.
>
>RFC 4190
>
>Title:
>    Framework for Supporting Emergency Telecommunications
>    Service (ETS) in IP Telephony
>
>Abstract:
>    This document presents a framework for supporting authorized,
>    emergency-related communication within the context of IP telephony.
>    We present a series of objectives that reflect a general view of how
>    authorized emergency service, in line with the Emergency
>    Telecommunications Service (ETS), should be realized within today's
>    IP architecture and service models.  From these objectives, we
>    present a corresponding set of protocols and capabilities, which
>    provide a more specific set of recommendations regarding existing
>    IETF protocols.  Finally, we present two scenarios that act as
>    guiding models for the objectives and functions listed in this
>    document.  These models, coupled with an example of an existing
>    service in the Public Switched Telephone Network (PSTN), contribute
>    to a constrained solution space.
>
>RFC 4375
>
>Title:
>    Emergency Telecommunications Services (ETS) Requirements
>    for a Single Administrative Domain
>
>Abstract:
>    This document presents a list of requirements in support of Emergency
>    Telecommunications Service (ETS) within a single administrative
>    domain.  This document focuses on a specific set of administrative
>    constraints and scope.  Solutions to these requirements are not
>    presented in this document.
>
>
>TSV Working Group
>
>RFC 4542
>
>Title:
>    Implementing an Emergency Telecommunications Service (ETS)
>    for Real-Time Services in the Internet Protocol Suite
>
>Abstract:
>    RFCs 3689 and 3690 detail requirements for an Emergency
>    Telecommunications Service (ETS), of which an Internet Emergency
>    Preparedness Service (IEPS) would be a part.  Some of these types of
>    services require call preemption; others require call queuing or
>    other mechanisms.  IEPS requires a Call Admission Control (CAC)
>    procedure and a Per Hop Behavior (PHB) for the data that meet the
>    needs of this architecture.  Such a CAC procedure and PHB is
>    appropriate to any service that might use H.323 or SIP to set up
>    real-time sessions.  The key requirement is to guarantee an elevated
>    probability of call completion to an authorized user in time of
>    crisis.
>
>    This document primarily discusses supporting ETS in the context of
>    the US Government and NATO, because it focuses on the Multi-Level
>    Precedence and Preemption (MLPP) and Government Emergency
>    Telecommunication Service (GETS) standards.  The architectures
>    described here are applicable beyond these organizations.
>
>Work In Progress:   draft-ietf-tsvwg-emergency-rsvp-03.txt
>
>Title:
>    Resource ReSerVation Protovol (RSVP) Extensions for
>    Emergency Services
>
>Abstract:
>    An Emergency Telecommunications Service (ETS) requires the ability to
>    provide an elevated probability of session establishment to an
>    authorized user in times of network congestion (typically, during a
>    crisis). When supported over the Internet Protocol suite, this may be
>    facilitated through a network layer admission control solution, which
>    supports prioritized access to resources (e.g., bandwidth). These
>    resources may be explicitly set aside for emergency services, or they
>    may be shared with other sessions.
>
>   This document specifies RSVP extensions that can be used to support
>    such an admission priority capability at the network layer. Note that
>    these extensions represent one possible solution component in
>    satisfying ETS requirements. Other solution components, or other
>    solutions, are outside the scope of this document.
>
>NSIS Working Group
>
>Work In Progress: draft-ietf-nsis-qos-nslp-14.txt
>
>Title:
>NSLP for Quality-of-Service Signaling
>
>Abstract:
>This specification describes the NSIS Signaling=20
>Layer Protocol (NSLP) for signaling QoS=20
>reservations in the Internet.  It is in=20
>accordance with the framework and requirements=20
>developed in NSIS.  Together with GIST, it=20
>provides functionality similar to RSVP and=20
>extends it.  The QoS NSLP is independent of the=20
>underlying QoS specification or architecture and=20
>provides support for different reservation=20
>models. It is simplified by the elimination of=20
>support for multicast flows. This specification=20
>explains the overall protocol approach, design=20
>decisions made and provides examples.  It=20
>specifies object, message  formats and processing rules.
>
>DIME Working Group
>
>Work In Progress: draft-ietf-dime-diameter-qos-01.txt
>
>Title:
>   Diameter Quality of Service Application
>
>Abstract:
>   This document describes a Diameter application that performs
>   Authentication, Authorization, and Accounting for Quality of Service
>   (QoS) reservations.  This protocol is used by elements along the path
>   of a given application flow to authenticate a reservation request,
>   ensure that the reservation is authorized, and to account for
>   resources consumed during the lifetime of the application flow.
>   Clients that implement the Diameter QoS application contact an
>   authorizing entity/application server that is located somewhere in
>   the network, allowing for a wide variety of flexible deployment
>   models.
>
>Work In Progress: draft-ietf-dime-qos-parameters-00.txt
>
>Title:
>   Quality of Service Parameters for Usage with the AAA Framework
>
>Abstract:
>   This document defines a number of Quality of Service (QoS) parameters
>   that can be reused for conveying QoS information within RADIUS and
>   Diameter.
>
>   The payloads used to carry these QoS parameters are opaque for the
>   AAA client and the AAA server itself and interpreted by the
>   respective Resource Management Function.
>
>Work In Progress: draft-ietf-dime-qos-attributes-01.txt
>
>Title:
>   Quality of Service Attributes for Diameter and RADIUS
>
>Abstract:
>   This document extends the functionality of the Diameter Base protocol
>   and other Diameter applications with respect to their ability to
>   convey Quality of Service information.  The AVPs defined in this
>   document are also available for Remote Authentication Dial In User
>   Service (RADIUS).
>
>
>Non-WG Documents
>
>         Approved for publication: draft-carlberg-trip-attribute-rp-02.txt
>
>         Title:
>           TRIP Attribute for Resource Priority
>
>Abstract:
>    This document defines a new attribute for  the  TRIP  protocol.   The
>    attribute   associates   protocols/services   in  the  PSTN  offering
>    authorized  prioritization  during  call  setup  that  are  reachable
>    through  a TRIP gateway.  Current examples of preferential service in
>    the PSTN are Government Emergency Telecommunications  Service  (GETS)
>    in  the U.S. and Government Telephone Preference Scheme (GTPS) in the
>    U.K.  The proposed attribute for TRIP is based on the NameSpace.Value
>    tupple defined for the SIP resource Priority field.
>
>
>
>
>Magnus Westerlund
>
>IETF Transport Area Director & TSVWG Chair
>----------------------------------------------------------------------
>Multimedia Technologies, Ericsson Research EAB/TVM/M
>----------------------------------------------------------------------
>Ericsson AB                | Phone +46 8 4048287
>Torshamsgatan 23           | Fax   +46 8 7575550
>S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>----------------------------------------------------------------------
>
>
>_______________________________________________
>nsis mailing list
>nsis@ietf.org
>https://www1.ietf.org/mailman/listinfo/nsis





From tsvwg-bounces@ietf.org Wed Aug 29 10:25:54 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQOSh-0004jD-0x; Wed, 29 Aug 2007 10:24:03 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IQOSg-0004id-7k
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 29 Aug 2007 10:24:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQOSf-0004fo-FK; Wed, 29 Aug 2007 10:24:01 -0400
Received: from ccsmtpgate.mugla.edu.tr ([194.27.32.25]
	helo=ccsmtpgate.mu.edu.tr) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IQOSa-00010l-6b; Wed, 29 Aug 2007 10:24:01 -0400
Received: from ccexc01.mu.edu.tr ([10.1.1.15]) by ccsmtpgate.mu.edu.tr with
	Microsoft SMTPSVC(6.0.3790.3959); Wed, 29 Aug 2007 17:29:36 +0300
Received: from mail pickup service by ccexc01.mu.edu.tr with Microsoft SMTPSVC;
	Wed, 29 Aug 2007 17:29:34 +0300
Received: from megatron.ietf.org ([156.154.16.145]) by ccsmtpgate.mu.edu.tr
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 28 Aug 2007 21:06:05 +0300
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQ5Li-0004xP-0F; Tue, 28 Aug 2007 13:59:34 -0400
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1IQ5Lg-0004wn-Mu
	for nsis-confirm+ok@megatron.ietf.org; Tue, 28 Aug 2007 13:59:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQ5Lg-0004wc-Ac; Tue, 28 Aug 2007 13:59:32 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IQ5Le-0000b0-OY; Tue, 28 Aug 2007 13:59:32 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-1.cisco.com with ESMTP; 28 Aug 2007 10:59:29 -0700
X-IronPort-AV: i="4.19,317,1183359600"; 
	d="scan'208"; a="15348078:sNHT40240212"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l7SHxTN2013270; 
	Tue, 28 Aug 2007 10:59:29 -0700
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 l7SHxClh008831;
	Tue, 28 Aug 2007 17:59:29 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Aug 2007 10:59:21 -0700
Received: from jmpolk-wxp.cisco.com ([10.21.123.166]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Aug 2007 10:59:21 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 28 Aug 2007 12:59:22 -0500
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [NSIS] Re: [Tsvwg] Re: [Sip] Re: Draft Liaison response to
	SG13 on Emergency Telecommunications
In-Reply-To: <46D3CFCF.6070308@ericsson.com>
References: <46AF5370.9020304@ericsson.com> <46D2E80E.8000001@ericsson.com>
	<XFE-SJC-211IFprhMOg0000051a@xfe-sjc-211.amer.cisco.com>
	<46D3CFCF.6070308@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Message-ID: <XFE-SJC-211H71yEXUI000006c7@xfe-sjc-211.amer.cisco.com>
X-OriginalArrivalTime: 28 Aug 2007 17:59:21.0205 (UTC)
	FILETIME=[2919EA50:01C7E99D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=14975; t=1188323969;
	x=1189187969; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jmpolk@cisco.com;
	z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com>
	|Subject:=20Re=3A=20[NSIS]=20Re=3A=20[Tsvwg]=20Re=3A=20[Sip]=20Re=3A=20Dr
	aft=20Liaison=20response=20to=0A=20=20SG13=20on=20Emergency=20Telecommunic
	ations |Sender:=20;
	bh=m99wFMraDniP/oabHCb59sGhsw2Bm5NRjjTI8QPmPjQ=;
	b=bODCQI96h2iutBG4vGsYcbj1e/Oo4s0WfBpHF2E8WSTSIdETsS+MhpFOBid8YxpSICPCI97d
	sdgboM6xqHbePJ1KuM3XLQaNN2jxktMXOXQIgqArKt8G+EV6TaxcEWe+;
Authentication-Results: sj-dkim-3; header.From=jmpolk@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 89ebdf268eceaeaf784b3acb625dc20e
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3dc828214e948ff35b815af10e94a823
Cc: sip@ietf.org, dime@ietf.org, IETF SIPPING WG <sipping@ietf.org>,
	tsvwg <tsvwg@ietf.org>, NSIS <nsis@ietf.org>
X-BeenThere: tsvwg@ietf.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

this is good with me

At 02:33 AM 8/28/2007, Magnus Westerlund wrote:
>Hi again,
>
>I have received some more comments. So here is=20
>an updated version adding DIME documents and correcting origin of=
 documents.
>
>
>Submission
>Date:           <tbd>, 2007
>
>From:           IETF Working groups TSVWG, NSIS, DIME, SIP and SIPPING
>
>To:             Georges Sebek  <tsbsg13@itu.int> ,
>                 Keith Knightson <kgk@igs.net>
>
>Cc:             Magnus Westerlund <magnus.westerlund@ericsson.com>,
>Lars Eggert <lars.eggert@nokia.com>,
>James Polk <jmpolk@cisco.com>,
>Martin Stiemerling <stiemerling@netlab.nec.de>,
>John Loughney <john.loughney@nokia.com>
>Dean Willis <dean.willis@softarmor.com>,
>Keith Drage <drage@alcatel-lucent.com>,
>Mary Barnes <mary.barnes@nortel.com>,
>Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>,
>Scott Bradner <sob@harvard.edu>,
>Kimberly King <ksking@mitre.org>,
>Scott Brim <swb@employees.org>,
>Hannes Tschofenig <Hannes.Tschofenig@gmx.net>,
>David Frascone <dave@frascone.com>
>
>Response
>Contact:        TSV WG (tsv-chairs@tools.ietf.org)
>                 NSIS (nsis-chairs@tools.ietf.org)
>                 SIPPING (sipping-chairs@tools.ietf.org)
>                 SIP (sip-chairs@tools.ietf.org)
>                 DIME (dime-chairs@tools.ietf.org)
>
>Purpose:        Response to Liaison Request
>
>Deadline:       None
>
>Title: Response to liaison request from ITU-T=20
>Study Group 13 work on emergency telecommunications
>
>This is a response to the liaison request made=20
>by Q.3/13 regarding emergency telecommunications=20
>(REF: NGN-GSI/DOC =AD 60 Rev.2). We would first=20
>like to apologize for failing to meet the=20
>deadline in responding. We do hope that the late=20
>answer still can be of some use.
>
>The liaison request was made to the following=20
>working groups (WG): IEPREP, TSVWG, and NSIS.=20
>Since the request was sent the IEPREP WG has=20
>concluded. In addition to the WGs from which=20
>information was requested, we also think that=20
>work performed by the DIME, SIP and SIPPING WG may be of relevance.
>
>Pursuant to ITU-T Study Group 13 request for=20
>information on relevant and related work in the=20
>IETF regarding emergency communications, we list=20
>below RFCs and works in progress that we feel=20
>may be of interest to your group.  Some of the=20
>completed work is Informational, and others are=20
>in the category of Standards Track.
>
>Q.3/13 also requested that we keep you informed=20
>of any developments in regards to emergency=20
>telecommunications. In those regards we would=20
>like to make you aware that IETF mailing list=20
>participation and document information is free=20
>and open to anyone, allowing participants in=20
>Q.3/13 to keep themselves informed of any=20
>developments. If Q.3/13 desire to get further=20
>information about specific ongoing work, then=20
>please send a liaison request to the responsible=20
>WG for those specific documents.
>
>The following list is divided under the=20
>associated working groups from which the work has been done within the=
 IETF.
>
>
>SIP Working Group
>
>RFC 4412
>
>Title:
>    Communications Resource Priority for the Session Initiation
>    Protocol (SIP)
>
>Abstract:
>    This document defines two new Session Initiation Protocol (SIP)
>    header fields for communicating resource priority, namely,
>    "Resource-Priority" and "Accept-Resource-Priority".  The
>    "Resource-Priority" header field can influence the behavior of SIP
>    user agents (such as telephone gateways and IP telephones) and SIP
>    proxies.  It does not directly influence the forwarding behavior of
>    IP routers.
>
>         The below two documents are proposed=20
> work items accepted to become IETF WG items are=20
> likely of interest as they update RFC 4412.
>
>Work In Progress:   draft-polk-sip-rph-in-responses-00
>
>Title:
>Allowing SIP Resource Priority Header in SIP Responses
>
>Abstract:
>    The Session Initiation Protocol (SIP) Resource Priority Header
>    (RPH), in its current form, is ignored in SIP responses.  This was a
>    design choice during RFC 4412's development. This is now considered
>    a bad design choice in certain scenarios.  This document corrects
>    RFC 4412's communications model by optionally allowing a SIP server
>    or user agent client to process the Resource-Priority Header in a
>    response.
>
>Work In Progress:   draft-polk-sip-rph-new-namespaces--00
>
>Title:
>New Session Initiation Protocol=20
>Resource-Priority Header Namespaces for the Defense Information Systems=
 Agency
>
>Abstract:
>    This document creates additional Session Initiation Protocol
>    Resource-Priority header namespaces, to be IANA registered.  This
>    document intends to update RFC 4412, as a Proposed Standard document
>    if published by the RFC-Editor.
>
>
>
>SIPPING Working Group
>
>RFC 4411
>
>Title:
>    Extending the Session Initiation Protocol (SIP)
>    Reason Header for Preemption Events
>
>Abstract:
>   This document proposes an IANA Registration extension to the Session
>    Initiation Protocol (SIP) Reason Header to be included in a BYE
>    Method Request as a result of a session preemption event, either at a
>    user agent (UA), or somewhere in the network involving a
>    reservation-based protocol such as the Resource ReSerVation Protocol
>    (RSVP) or Next Steps in Signaling (NSIS).  This document does not
>    attempt to address routers failing in the packet path; instead, it
>    addresses a deliberate tear down of a flow between UAs, and informs
>    the terminated UA(s) with an indication of what occurred.
>
>IEPREP Working Group
>
>RFC 3487
>
>Title:
>    Requirements for Resource Priority Mechanisms for the
>    Session Initiation Protocol (SIP)
>
>Abstract:
>    This document summarizes requirements for prioritizing access to
>    circuit-switched network, end system and proxy resources for
>    emergency preparedness communications using the Session Initiation
>    Protocol (SIP).
>
>RFC 3689
>
>Title:
>    General Requirements for
>    Emergency Telecommunication Service (ETS)
>
>Abstract:
>    This document presents a list of general requirements in support of
>    Emergency Telecommunications Service (ETS).  Solutions to these
>    requirements are not presented in this document.  Additional
>    requirements pertaining to specific applications, or types of
>    applications, are to be specified in separate document(s).
>
>RFC 3690
>
>Title:
>    IP Telephony Requirements for
>    Emergency Telecommunication Service (ETS)
>
>Abstract:
>    This document presents a list of requirements in support of Emergency
>    Telecommunications Service (ETS) within the context of IP telephony.
>    It is an extension to the general requirements presented in RFC 3689.
>    Solutions to these requirements are not presented in this document.
>
>RFC 4190
>
>Title:
>    Framework for Supporting Emergency Telecommunications
>    Service (ETS) in IP Telephony
>
>Abstract:
>    This document presents a framework for supporting authorized,
>    emergency-related communication within the context of IP telephony.
>    We present a series of objectives that reflect a general view of how
>    authorized emergency service, in line with the Emergency
>    Telecommunications Service (ETS), should be realized within today's
>    IP architecture and service models.  From these objectives, we
>    present a corresponding set of protocols and capabilities, which
>    provide a more specific set of recommendations regarding existing
>    IETF protocols.  Finally, we present two scenarios that act as
>    guiding models for the objectives and functions listed in this
>    document.  These models, coupled with an example of an existing
>    service in the Public Switched Telephone Network (PSTN), contribute
>    to a constrained solution space.
>
>RFC 4375
>
>Title:
>    Emergency Telecommunications Services (ETS) Requirements
>    for a Single Administrative Domain
>
>Abstract:
>    This document presents a list of requirements in support of Emergency
>    Telecommunications Service (ETS) within a single administrative
>    domain.  This document focuses on a specific set of administrative
>    constraints and scope.  Solutions to these requirements are not
>    presented in this document.
>
>
>TSV Working Group
>
>RFC 4542
>
>Title:
>    Implementing an Emergency Telecommunications Service (ETS)
>    for Real-Time Services in the Internet Protocol Suite
>
>Abstract:
>    RFCs 3689 and 3690 detail requirements for an Emergency
>    Telecommunications Service (ETS), of which an Internet Emergency
>    Preparedness Service (IEPS) would be a part.  Some of these types of
>    services require call preemption; others require call queuing or
>    other mechanisms.  IEPS requires a Call Admission Control (CAC)
>    procedure and a Per Hop Behavior (PHB) for the data that meet the
>    needs of this architecture.  Such a CAC procedure and PHB is
>    appropriate to any service that might use H.323 or SIP to set up
>    real-time sessions.  The key requirement is to guarantee an elevated
>    probability of call completion to an authorized user in time of
>    crisis.
>
>    This document primarily discusses supporting ETS in the context of
>    the US Government and NATO, because it focuses on the Multi-Level
>    Precedence and Preemption (MLPP) and Government Emergency
>    Telecommunication Service (GETS) standards.  The architectures
>    described here are applicable beyond these organizations.
>
>Work In Progress:   draft-ietf-tsvwg-emergency-rsvp-03.txt
>
>Title:
>    Resource ReSerVation Protovol (RSVP) Extensions for
>    Emergency Services
>
>Abstract:
>    An Emergency Telecommunications Service (ETS) requires the ability to
>    provide an elevated probability of session establishment to an
>    authorized user in times of network congestion (typically, during a
>    crisis). When supported over the Internet Protocol suite, this may be
>    facilitated through a network layer admission control solution, which
>    supports prioritized access to resources (e.g., bandwidth). These
>    resources may be explicitly set aside for emergency services, or they
>    may be shared with other sessions.
>
>   This document specifies RSVP extensions that can be used to support
>    such an admission priority capability at the network layer. Note that
>    these extensions represent one possible solution component in
>    satisfying ETS requirements. Other solution components, or other
>    solutions, are outside the scope of this document.
>
>NSIS Working Group
>
>Work In Progress: draft-ietf-nsis-qos-nslp-14.txt
>
>Title:
>NSLP for Quality-of-Service Signaling
>
>Abstract:
>This specification describes the NSIS Signaling=20
>Layer Protocol (NSLP) for signaling QoS=20
>reservations in the Internet.  It is in=20
>accordance with the framework and requirements=20
>developed in NSIS.  Together with GIST, it=20
>provides functionality similar to RSVP and=20
>extends it.  The QoS NSLP is independent of the=20
>underlying QoS specification or architecture and=20
>provides support for different reservation=20
>models. It is simplified by the elimination of=20
>support for multicast flows. This specification=20
>explains the overall protocol approach, design=20
>decisions made and provides examples.  It=20
>specifies object, message  formats and processing rules.
>
>DIME Working Group
>
>Work In Progress: draft-ietf-dime-diameter-qos-01.txt
>
>Title:
>   Diameter Quality of Service Application
>
>Abstract:
>   This document describes a Diameter application that performs
>   Authentication, Authorization, and Accounting for Quality of Service
>   (QoS) reservations.  This protocol is used by elements along the path
>   of a given application flow to authenticate a reservation request,
>   ensure that the reservation is authorized, and to account for
>   resources consumed during the lifetime of the application flow.
>   Clients that implement the Diameter QoS application contact an
>   authorizing entity/application server that is located somewhere in
>   the network, allowing for a wide variety of flexible deployment
>   models.
>
>Work In Progress: draft-ietf-dime-qos-parameters-00.txt
>
>Title:
>   Quality of Service Parameters for Usage with the AAA Framework
>
>Abstract:
>   This document defines a number of Quality of Service (QoS) parameters
>   that can be reused for conveying QoS information within RADIUS and
>   Diameter.
>
>   The payloads used to carry these QoS parameters are opaque for the
>   AAA client and the AAA server itself and interpreted by the
>   respective Resource Management Function.
>
>Work In Progress: draft-ietf-dime-qos-attributes-01.txt
>
>Title:
>   Quality of Service Attributes for Diameter and RADIUS
>
>Abstract:
>   This document extends the functionality of the Diameter Base protocol
>   and other Diameter applications with respect to their ability to
>   convey Quality of Service information.  The AVPs defined in this
>   document are also available for Remote Authentication Dial In User
>   Service (RADIUS).
>
>
>Non-WG Documents
>
>         Approved for publication: draft-carlberg-trip-attribute-rp-02.txt
>
>         Title:
>           TRIP Attribute for Resource Priority
>
>Abstract:
>    This document defines a new attribute for  the  TRIP  protocol.   The
>    attribute   associates   protocols/services   in  the  PSTN  offering
>    authorized  prioritization  during  call  setup  that  are  reachable
>    through  a TRIP gateway.  Current examples of preferential service in
>    the PSTN are Government Emergency Telecommunications  Service  (GETS)
>    in  the U.S. and Government Telephone Preference Scheme (GTPS) in the
>    U.K.  The proposed attribute for TRIP is based on the NameSpace.Value
>    tupple defined for the SIP resource Priority field.
>
>
>
>
>Magnus Westerlund
>
>IETF Transport Area Director & TSVWG Chair
>----------------------------------------------------------------------
>Multimedia Technologies, Ericsson Research EAB/TVM/M
>----------------------------------------------------------------------
>Ericsson AB                | Phone +46 8 4048287
>Torshamsgatan 23           | Fax   +46 8 7575550
>S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>----------------------------------------------------------------------
>
>
>_______________________________________________
>nsis mailing list
>nsis@ietf.org
>https://www1.ietf.org/mailman/listinfo/nsis


_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis





From tsvwg-bounces@ietf.org Wed Aug 29 17:13:45 2007
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQUpX-0005pL-Uw; Wed, 29 Aug 2007 17:12:04 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43)
	id 1IQUpK-0005Gy-Lh
	for tsvwg-confirm+ok@megatron.ietf.org; Wed, 29 Aug 2007 17:11:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQUpI-0005Ep-SE; Wed, 29 Aug 2007 17:11:49 -0400
Received: from bosco.isi.edu ([128.9.168.207])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IQUpH-00024a-Ku; Wed, 29 Aug 2007 17:11:48 -0400
Received: by bosco.isi.edu (Postfix, from userid 70)
	id 40A27E0449; Wed, 29 Aug 2007 14:09:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20070829210956.40A27E0449@bosco.isi.edu>
Date: Wed, 29 Aug 2007 14:09:56 -0700 (PDT)
X-Spam-Score: -15.0 (---------------)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [Tsvwg] RFC 4895 on Authenticated Chunks for the Stream Control
	Transmission Protocol (SCTP)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4895

        Title:      Authenticated Chunks for the Stream 
                    Control Transmission Protocol (SCTP) 
        Author:     M. Tuexen, R. Stewart,
                    P. Lei, E. Rescorla
        Status:     Standards Track
        Date:       August 2007
        Mailbox:    tuexen@fh-muenster.de, 
                    rrs@cisco.com, 
                    peterlei@cisco.com,  ekr@rtfm.com
        Pages:      19
        Characters: 42507
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-sctp-auth-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4895.txt

This document describes a new chunk type, several parameters, and
procedures for the Stream Control Transmission Protocol (SCTP).  This
new chunk type can be used to authenticate SCTP chunks by using
shared keys between the sender and receiver.  The new parameters are
used to establish the shared keys.  [STANDARDS TRACK]

This document is a product of the Transport Area Working Group
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.Please refer to the current edition of the Internet
 Official Protocol Standards (STD 1) for the standardization state and
 status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...







