Last Modified: 2005-01-07
|Done||Submit 'Signaling Requirements' to IESG for publication as an Informational RFC.|
|Done||Submit 'Next Steps in Signaling: Framework' to IESG for publication as Informational RFC|
|Done||Submit 'Analysis of Existing Signaling Protocols' to IESG as Informational RFC|
|Done||Submit 'RSVP Security Properties' to IESG as Informational RFC|
|Done||Submit 'NSIS Threats' to IESG as Informational RFC|
|Apr 05||Submit 'NSIS Transport Protocol' to IESG for publication for Proposed Standard|
|May 05||Submit 'NSIS QoS Application Protocol' to IESG for publication for Proposed Standard|
|May 05||Submit 'NSIS QoS Specification Template' to IESG for publication as an Informational RFC|
|Jun 05||Submit 'NSIS Middle Box Signaling Application Protocol' to IESG for publication for Proposed Standard|
|Sep 05||Submit 'Applicability Statement of NSIS Protocols in Mobile Environments' to the IESG as an Informational RFC|
|Sep 05||Submit 'Differentiated Service Signaling on the Internet' to the IESG for publication as an Informational RFC|
|RFC3583||I||Requirements of a Quality of Service (QoS)Solution for Mobile IP|
|RFC3726||I||Requirements for Signaling Protocols|
Next Steps in Signaling WG (nsis)
Tuesday, March 8 at 1645-1745
CHAIR: John Loughney <email@example.com>
Minutes compiled by Hannes Tschofenig
Unofficial Weblog: http://www.ietf-nsis.org
- John (John Loughney)
Three major issues still open:
2. Adding Routing State Setup
GIMPS state machine
Most of the work mainly done by students Cedric, Xiaoming and Hannes works with.
- Two modeling paradigms:
- Want to check out the simplified state machine using the
- Do we want to have a separate state machine document or
NSIS Mobility Applicability
Main issue #4
Next Steps: See slides.
UpToHere on Tuesday
Discuss this on Thur, presented by Juergen.
This work is also interested by other WG (IPFIX) that may be discussed
THURSDAY, March 10, 2005
Hannes on the mike:
We have discussed security threats for some time and described them in a separate threats document.
A few selected issues have been discussed on the mailing list over the last few months (related to the 'receiver behind the nat' case).
Now, the security threats and the security requirements being completed we have intergrated the threats document into the main document.
The solution section has been updated but not yet finalized.
Discussions with regard to mobility and security are still necessary and will
be done together with the nsis mobility folks.
3GPP2 FW Signaling Requirements
These requirements are from the 3GPP2 prospective.
Pinhole Creation Requirements
Going over the Firewall Features Req:
John indicated that these are requirements from another standards org,
Hannes: The document is very interesting input for us.
Some of the requirements are already fulfilled with the most recent draft version.
Some others can be addressed and again some others need further discussion.
Martin: about 80% of these requirements are already being handled.
Cedric: indicating that some of these are dynamic FW configs, some are static
Bob Braden: Some of the req uses "should" and "must" in a funny way, may need
Dave Oran: Posting issues with routing changes, etc.
Bob Braden: disagree with what David Black says, that many of the parameters
There is a discussion between David Black, Dave Oran, and Bob Braden on
Georgios indicated some suggestions on usage of some boundary identification
QoS model based on ITU-T recommendation Y.1541.
Jerry: Next steps: Asking to make this a WG doc.
Bob Braden: this was good example of showing extensibility of QoS-NSLP/QSPEC
John: Who read the draft and who would support it as a WG item?
(About 10-15 hands up for each.)
Would like to discuss on the list and confirm interest in the WG before making this a WG doc.
Discusses severe congestion handling.
Discussed usage of congestion refresh messages.
David Black indicated re-use of 3168 instead of using new DSCP for
Talk about usage of ECN probes.
Discussed some issues raised in TSVWG on
Showing PDR Nonce mechanism.
David Black's concerns with ECN:
John asks Allison (as TSVWG WG chair and Transport AD)
Franciou of Cisco indicates that the Severe Congestion condition is the
John: lets discuss this on the list and are welcoming the RT-ECN folks
- address "three party token based" approach.
Some issues for NSIS signaling
Issues: Multiple Paths Support.