[Ieprep] Fw: WG Review: Recharter of Internet Emergency Preparedness (ieprep)

Janet P Gunn <jgunn6@csc.com> Thu, 02 November 2006 21:51 UTC

Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GfkTf-0007lz-PP; Thu, 02 Nov 2006 16:51:59 -0500
Received: from [] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GfkTe-0007lu-P8 for ieprep@ietf.org; Thu, 02 Nov 2006 16:51:58 -0500
Received: from amer-mta08.csc.com ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GfkTd-0002if-Eu for ieprep@ietf.org; Thu, 02 Nov 2006 16:51:58 -0500
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com []) by amer-mta08.csc.com (Switch-3.1.6/Switch-3.1.0) with ESMTP id kA2Lpt4N019363 for <ieprep@ietf.org>; Thu, 2 Nov 2006 16:51:55 -0500 (EST)
To: ieprep@ietf.org
X-Mailer: Lotus Notes 652HF83 November 04, 2004
Message-ID: <OF9AD93CBE.D4AC77F5-ON8525721A.00780EEF-8525721A.00781B6C@csc.com>
From: Janet P Gunn <jgunn6@csc.com>
Date: Thu, 02 Nov 2006 16:51:53 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 6.5.3|September 14, 2004) at 11/02/2006 04:50:48 PM
MIME-Version: 1.0
Content-type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Subject: [Ieprep] Fw: WG Review: Recharter of Internet Emergency Preparedness (ieprep)
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>
Errors-To: ieprep-bounces@ietf.org

----- Forwarded by Janet P Gunn/FED/CSC on 11/02/2006 04:51 PM -----

ken carlberg <carlberg@g11.org.uk> wrote on 11/02/2006 03:03:15 PM:

> >     ken> Interestingly enough, the work that you mention below in your
> >     ken> original posting...
> >     ken> ... rfc-4542, rfc-4411, and draft
> >     ken> -ietf-tsvwg-vpn-signal-preemption  (along with some other
> >     ken> related work) has actually not been done in IEPREP because
> >     ken> the group was not allowed to consider solutions.  Instead,
> >     ken> some of the work has been pushed to TSVWG, to the groans and
> >     ken> sometimes confusion of some of the participants of that
> >     ken> group, who wondered what the subject of prioritization had to
> >     ken> do with TSVWG.  Part
> >
> > I think the work you cite belongs in tsvwg.  AT least 4542 and
> > vpn-signaling-preemption.
> I mentioned the above as examples, not as a case-by-case examination
> of what should or should not be in IEPREP.  But along those lines,
> rfc-4542 (titled "Implementing an Emergency Telecommunications
> Service"), where ETS was first established in IEPREP and the draft
> deals with priority and preemption, seems odd to me to be in TSVWG.
> But if you feel differently, then we agree to disagree.
> >     ken> of the revised charter is meant to
> >     ken> remove this obstacle.
> >
> > Which work would be permitted under the revised charter that is
> > currently udone elsewhere?  I may have more concerns about the revised
> > charter than I thought I did.
> I am not speaking of any specific work other than what has been
> discussed in the proposed re-charter.  to consider otherwise is to go
> beyond what I stated.
> >     ken> Also, as Scott Brimm has mentioned, there is a proposed
> >     ken> liaison from the ITU to work with the IETF, with one of the
> >     ken> working groups of interest being IEPREP.  It would seem
> >     ken> odd to close down the group and punt the subject to them when
> >     ken> they are approaching "us" for assistance  If IEPREP is
> >     ken> closed, does that mean the subject gets pushed over to TSVWG?
> >
> >
> > that rather depends on what question they're asking, now doesn't it?
> > IF they're asking for enhancements to RSVP to deal with some ETS
> > issues, then yes, I'd hope the work would be done in tsvwg.  That way,
> > ETS requirements can be balanced against other requirements.  If they
> > want to change SIP, I'd hope that it would go through sipping and
> > eventually sip.
> we will have to wait to see what they request.  all I stated was that
> they were coming to us and that it was odd to close down a group they
> were interested in working with.  Anticipating hypotheticals are not
> useful because they can put us down a rat hole that may or may not
> have substance.
> -ken
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf

Ieprep mailing list