IETF Logo Mail Archive

RE: [Ieprep] Re-charter?

"King, Kimberly S." <KIMBERLY.S.KING@saic.com> Tue, 19 July 2005 15:34 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Duu7U-0000vn-5u; Tue, 19 Jul 2005 11:34:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Duu7S-0000qk-3d for ieprep@megatron.ietf.org; Tue, 19 Jul 2005 11:34:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06930 for <ieprep@ietf.org>; Tue, 19 Jul 2005 11:34:51 -0400 (EDT)
Received: from mclmx.mail.saic.com ([149.8.64.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Duub5-0008Od-3d for ieprep@ietf.org; Tue, 19 Jul 2005 12:05:33 -0400
Received: from [149.8.64.21] by mclmx.mail.saic.com; Tue, 19 Jul 2005 11:34:34 -0400
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12]) by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id M2005071911343119375 ; Tue, 19 Jul 2005 11:34:33 -0400
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2657.72) id <PH3VGY4M>; Tue, 19 Jul 2005 11:34:30 -0400
Message-Id: <D24D16A6707B0A4B9EF084299CE99B39235F6FF7@mcl-its-exs02.mail.saic.com>
From: "King, Kimberly S." <KIMBERLY.S.KING@saic.com>
To: an.p.nguyen@dhs.gov, "King, Kimberly S." <KIMBERLY.S.KING@saic.com>
Subject: RE: [Ieprep] Re-charter?
Date: Tue, 19 Jul 2005 11:33:52 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: sob@harvard.edu, "Ieprep (ieprep@ietf.org)" <ieprep@ietf.org>
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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>
Sender: ieprep-bounces@ietf.org
Errors-To: ieprep-bounces@ietf.org

An,


>>1. Conveying information about the priority of specific 
>>flows (or sessions) that originate in a VoIP environment.  
>>This could include a requirements effort to describe 
>>extensions to NSIS or RSVP. Requirements for NSIS would be 
>>forwarded to the NSIS working group. Requirements for RSVP 
>>could be forwarded to tsvwg or worked on in IEPREP.

>I notice some solutions to providing the priority of traffic in association
>with QoS have been addressed in NSIS.

>I would like to how RSVP extensions can be used to address these
>requirements.

The intended charter isn't to presuppose a solution.  The above was an
example of what might be in scope and a practical avenue for progress within
the group.  

Since you have asked me about "how" extensions could be used, off hand I'd
point to RFC 2750, but again the charter discussion is not to discuss exact
solutions so let's leave it at that until it is decided what should be done.

Kimberly


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

v2.23.0 | Report a Bug | By Email