[Ieprep] Re: ETS (was Re: [Tsvwg] <draft-lefaucheur-emergency-rsvp> : Preemption scope)

"Brian F. G. Bidulock" <bidulock@openss7.org> Tue, 06 June 2006 23:53 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnlMb-0007ZU-FA; Tue, 06 Jun 2006 19:53:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnlMZ-0007ZE-B4; Tue, 06 Jun 2006 19:53:31 -0400
Received: from gw.openss7.com ([142.179.199.224]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnlMX-0004EZ-Nq; Tue, 06 Jun 2006 19:53:31 -0400
Received: from ns.pigworks.openss7.net (IDENT:b9DerVvvGSZ1QyJJF1JWd7ZK1hJpNzrk@ns1.evil.openss7.net [192.168.9.1]) by gw.openss7.com (8.11.6/8.11.6) with ESMTP id k56NrSq22425; Tue, 6 Jun 2006 17:53:28 -0600
Received: (from brian@localhost) by ns.pigworks.openss7.net (8.11.6/8.11.6) id k56NrSq13393; Tue, 6 Jun 2006 17:53:28 -0600
Date: Tue, 6 Jun 2006 17:53:28 -0600
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: ken carlberg <carlberg@g11.org.uk>
Message-ID: <20060606175328.A13072@openss7.org>
Mail-Followup-To: ken carlberg <carlberg@g11.org.uk>, tsvwg <tsvwg@ietf.org>, ieprep@ietf.org
References: <20060606121528.A7702@openss7.org> <28F05913385EAC43AF019413F674A0170DE0C7F9@OCCLUST04EVS1.ugd.att.com> <20060606122153.B7702@openss7.org> <57110167-E0A5-4AB6-BAD5-A78AED814D3D@g11.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <57110167-E0A5-4AB6-BAD5-A78AED814D3D@g11.org.uk>; from carlberg@g11.org.uk on Tue, Jun 06, 2006 at 07:19:29PM -0400
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: tsvwg <tsvwg@ietf.org>, ieprep@ietf.org
Subject: [Ieprep] Re: ETS (was Re: [Tsvwg] <draft-lefaucheur-emergency-rsvp> : Preemption scope)
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=subscribe>
Errors-To: ieprep-bounces@ietf.org

ken,

ken carlberg wrote:                              (Tue, 06 Jun 2006 19:19:29)
> I've cc'ed the IEPREP list since nearly all of the above documents  
> came from that group.  I kindly ask that if people choose to continue  
> the discussion on ETS, please drop the TSVWG from the cc list and  
> continue it on IEPREP.

Well, RFC 4190 section 4.3 explicitly scopes out network traffic
engineering in support of ETS.  Also, from the ieprep charter:

 "It is out of scope for this working group to do protocol or protocol
  feature development."

Whereas, as you should known as an author,
draft-lefaucheur-emergency-rsvp-01 clearly indicates:

 "This document specifies RSVP extensions necessary for supporting such
  admission priority capabilities."

I am confused by your request to drop tsvwg from the cc list: Is not
RSVP protocol and protocol feature development within the tsvwg charter?

--brian

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

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