headers
Ash, Gerald R (Jerry), ALABS | 1 Aug 2005 11:50
Picon
Favicon

Precedence/Priority Requirements for MLPP/Assured-Services & NSIS Work in Progress

All,

Following up on Tony DeSimone's and An Nguyen's presentations this
morning at the IEPREP meeting regarding priority/precedence
requirements, it would be good for folks to be aware of the work of NSIS
http://ietf.org/html.charters/nsis-charter.html on QoS signaling.  In
particular, please take a look at
> QoS-NSLP
> http://ietf.org/internet-drafts/draft-ietf-nsis-qos-nslp-07.txt
> and QSPEC for QoS-NSLP
> http://ietf.org/internet-drafts/draft-ietf-nsis-qspec-05.txt
> 
> The latter document specifies several parameters for signaling
> priority: holding priority, preemption priority, reservation priority
> (latter including admission priority, RPH namespace, RPH priority).
> 
Requirements for 'MLPP/Assured-Services'  (not sure what it's called
now) may fit into the work already started in NSIS.

> Thanks,
> Jerry
Permalink | Reply | 0 comments |
headers
King, Kimberly S. | 1 Aug 2005 16:42
Picon
Favicon

Precedence and Preemption for the GIG Transport Services


You may find the slides from today's meeting here

http://www.apl.jhu.edu/Notes/DeSimone/IETF/IEPREP/Paris/P&P_ietf_ieprep_31ju
l2005.pdf
Permalink | Reply | 0 comments |
headers
Kwok-Ho Chan | 26 Aug 2005 18:05
Favicon

After IEPREP WG meeting in Paris

Hi:
I noticed that Proceedings Submission Cut-Off date for the 63rd IETF at 
Paris is
Friday Sept 02, 2005, which is one week away.
I have not seen the IEPREP Working Group Meeting Notes/Minutes posted on the
IEPREP WG Mailing List yet.  Shouldn't the content of the meeting notes/minutes
be reviewed by the WG on the WG mailing list prior to their submission to 
proceedings?

What about the Re-Chartering discussions?
Wasn't there supposed to be changes to the proposed new charter to be posted on
the list so further discussion on this topic can continue on this list (for 
people who
did not attend the meeting in Paris)?

Thanks!
-- Kwok --
Permalink | Reply | 0 comments |
headers
King, Kimberly S. | 26 Aug 2005 18:45
Picon
Favicon

RE: After IEPREP WG meeting in Paris

Kwok,

The ieprep minutes are here
http://www3.ietf.org/proceedings/05aug/minutes/ieprep.html

The re-chartering discussion will start soon... 

Kimberly
Permalink | Reply | 0 comments |
headers
Kwok-Ho Chan | 26 Aug 2005 21:41
Favicon

RE: After IEPREP WG meeting in Paris

Kimberly:
Thank you very much!
Will be providing any comments on the minute's content to the list.
-- Kwok --

At 12:45 PM 8/26/2005, King, Kimberly  S. wrote:
>Kwok,
>
>The ieprep minutes are here
>http://www3.ietf.org/proceedings/05aug/minutes/ieprep.html
>
>The re-chartering discussion will start soon...
>
>Kimberly
Permalink | Reply | 0 comments |
headers
Kwok-Ho Chan | 30 Aug 2005 21:25
Favicon

RE: After IEPREP WG meeting in Paris

Kimberly:
My Thanks to the note takers.
And thank you very much for posting the meeting minutes to the IEPREP list.

I have made clarifications/corrections to the provided 63rd IETF IEPREP
WG Meeting Minutes.
The clarifications/corrections can be summarized as follows:
1. The hum indicated support for re-chartering in its current spirit with 
wording
     to be agreed on the mailing list.
2. The Working Group needs to have clear requirements before assuming any
     solutions or framework that satisfy the requirements.
3. Correction on my name, removing Paul: part or replacing Paul with Kwok.
4. Correction on name: Joe Babiarz.

I have included below the posted minutes with the clarifications/corrections
detailed, to assist the minutes editor(s) task.

Thank you again for the opportunity to review the meeting minutes before
they are finalized in the 63rd IETF Proceedings.
-- Kwok Ho Chan --

Posted minutes with clarifications/corrections:

>IEPREP Working Group Meeting at IETF-63
>
>The IEPREP Working Group was chaired by Kimberly King at the Paris IETF-63 
>on Monday August 1, 2005. (Scott Bradner, the other Co-Chair, was unable 
>to attend the Paris IETF meeting but was listening to the audio stream.)
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
James M. Polk | 30 Aug 2005 23:06
Picon
Favicon

RE: After IEPREP WG meeting in Paris

Kwok

While I agree that requirements are always necessary before solutions - 
this doesn't mean we start from square one on this. There are requirements 
RFCs in this WG already and TSVWG has a working solution (going to WGLC as 
soon as Allison posts the message she said was posted during the TSVWG 
meeting) to at least base future work on in IEPREP - which is the language 
of the recharter. That effort *is not* claiming victory or a raised white 
flag saying this is "it" for IEPREP for government networks. That effort is 
a data-path-coupled control plane solution, of which I do not believe there 
are any others.

There is room for additional documents in the new charter or future 
recharters, based on WG consensus.  These can come from the Gap Analysis ID 
to be done fairly early in the recharter's timeline.  I believe it would be 
premature to offer new documents into the IEPREP recharter that the WG has 
not seen before. MLPP-That-Works was reviewed by IEPREP and was given a 
green light to TSVWG to progress, since, at the time (and still now), 
IEPREP cannot work on solutions for government networks.

At 03:25 PM 8/30/2005 -0400, Kwok-Ho Chan wrote:
>Kimberly:
>My Thanks to the note takers.
>And thank you very much for posting the meeting minutes to the IEPREP list.
>
>I have made clarifications/corrections to the provided 63rd IETF IEPREP
>WG Meeting Minutes.
>The clarifications/corrections can be summarized as follows:
>1. The hum indicated support for re-chartering in its current spirit with 
>wording
(Continue reading)

Permalink | Reply | 1 comment |
headers
Kwok-Ho Chan | 30 Aug 2005 23:30
Favicon

RE: After IEPREP WG meeting in Paris

James:
The E-Mail I sent was just to clarify the minutes of the 63rd IETF IEPREP WG
session in Paris.  With the draft and event status at the time of the meeting.
Please do not read anything more than just that.

IMHO, we should start/continue discussing the IEPREP re-chartering on this
(IEPREP) list.   But IMHO, that should be a different E-Mail thread.

And discussion of the MLPP draft as its own E-Mail thread here or on
TSVWG list as suggested.
Thanks!
-- Kwok --

At 05:06 PM 8/30/2005, James M. Polk wrote:
>Kwok
>
>While I agree that requirements are always necessary before solutions - 
>this doesn't mean we start from square one on this. There are requirements 
>RFCs in this WG already and TSVWG has a working solution (going to WGLC as 
>soon as Allison posts the message she said was posted during the TSVWG 
>meeting) to at least base future work on in IEPREP - which is the language 
>of the recharter. That effort *is not* claiming victory or a raised white 
>flag saying this is "it" for IEPREP for government networks. That effort 
>is a data-path-coupled control plane solution, of which I do not believe 
>there are any others.
>
>There is room for additional documents in the new charter or future 
>recharters, based on WG consensus.  These can come from the Gap Analysis 
>ID to be done fairly early in the recharter's timeline.  I believe it 
>would be premature to offer new documents into the IEPREP recharter that
(Continue reading)

Permalink | Reply | 0 comments |
headers
James M. Polk | 31 Aug 2005 00:40
Picon
Favicon

RE: After IEPREP WG meeting in Paris

Kwok

At 05:30 PM 8/30/2005 -0400, Kwok-Ho Chan wrote:
>James:
>The E-Mail I sent was just to clarify the minutes of the 63rd IETF IEPREP WG
>session in Paris.  With the draft and event status at the time of the meeting.
>Please do not read anything more than just that.

ok

>IMHO, we should start/continue discussing the IEPREP re-chartering on this
>(IEPREP) list.   But IMHO, that should be a different E-Mail thread.

ok

>And discussion of the MLPP draft as its own E-Mail thread here or on
>TSVWG list as suggested.

ok

>Thanks!
>-- Kwok --

cheers,
James

                                 *******************
                 Truth is not to be argued... it is to be presented.
Permalink | Reply | 1 comment |
headers
King, Kimberly S. | 31 Aug 2005 01:12
Picon
Favicon

Proposed Revised Charter


Below is an updated proposed charter for WG review.

---

Internet Emergency Preparedness (ieprep) Charter  

Description of Working Group:  

Effective telecommunications capabilities are imperative to facilitate  
immediate recovery operations for serious disaster events including  
natural disasters (e.g., hurricanes, floods, earthquakes) and those  
created by man (e.g., terrorist attacks, combat situations or wartime  
events). In addition, related capabilities should be usable in normal  
command and control operations of military services, which often have  
timeliness requirements even in peacetime. 

Disasters can happen any time, any place, unexpectedly. Quick response  
for recovery operations requires immediate access to any public  
telecommunications capabilities at hand. These capabilities include:  
conventional telephone, cellular phones, and Internet access via online  
terminals, IP telephones, and wireless PDAs. The commercial  
telecommunications infrastructure is rapidly evolving to Internet-based  
technology. Therefore, the Internet community needs to consider how it  
can best support emergency management and recovery operations. 

The IEPREP WG will address proactive measures to congestion and recovery  
from various outages using three perspectives: 

1. A commercial (i.e., or public) telecommunications infrastructure
(Continue reading)

Permalink | Reply | 4 comments |

Gmane