WG Action: Conclusion of Next Steps in Signaling (nsis)

The Next Steps in Signaling (nsis) working group in the Transport Area has
concluded. The IESG contact persons are Lars Eggert and David Harrington.

The mailing list will be closed.

Re: thank you all!

A special thanks to all document authors, editors and reviewers, who 
spent a huge amount of time to make the RFCs become reality. We produced 
a good set of documents and created many good concepts and ideas towards 
a unifying signaling platform.

I hope we will see some deployment, in one form or another, in the 
coming years. Research projects have embraced our work, just need to get 
the industry interested.

regards,
Jukka

On 03/16/2011 10:45 AM, Lars Eggert wrote:
> Hi,
>
> with the publication of RFC5979 and RFC5980, the NSIS working group has successfully completed its
chartered work. Congratulations!
>
> I'd sincerely like to thank all participants, editors and chairs for their hard work over the years,
especially in the last phase, where new requirements from the IESG meant that a significant amount of
edits needed to be done in a synchronized way across almost the entire set of documents.
>
> I will proceed to close the NSIS WG and this mailing list. Please use the tsv-area <at> ietf.org list for any
future discussion of NSIS.
>
> Thanks again,
> Lars
>
>
>

thank you all!

Hi,

with the publication of RFC5979 and RFC5980, the NSIS working group has successfully completed its
chartered work. Congratulations!

I'd sincerely like to thank all participants, editors and chairs for their hard work over the years,
especially in the last phase, where new requirements from the IESG meant that a significant amount of
edits needed to be done in a synchronized way across almost the entire set of documents.

I will proceed to close the NSIS WG and this mailing list. Please use the tsv-area <at> ietf.org list for any
future discussion of NSIS.

Thanks again,
Lars

_______________________________________________
nsis mailing list
nsis <at> ietf.org
https://www.ietf.org/mailman/listinfo/nsis

RFC 5980 on NSIS Protocol Operation in Mobile Environments

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5980

        Title:      NSIS Protocol Operation in Mobile 
                    Environments 
        Author:     T. Sanda, Ed.,
                    X. Fu, S. Jeong,
                    J. Manner, H. Tschofenig
        Status:     Informational
        Stream:     IETF
        Date:       March 2011
        Mailbox:    sanda.takako <at> jp.panasonic.com, 
                    fu <at> cs.uni-goettingen.de, 
                    shjeong <at> hufs.ac.kr,  jukka.manner <at> tkk.fi, 
                    Hannes.Tschofenig <at> nsn.com
        Pages:      32
        Characters: 77323
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nsis-applicability-mobility-signaling-20.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5980.txt

Mobility of an IP-based node affects routing paths, and as a result,
can have a significant effect on the protocol operation and state
management.  This document discusses the effects mobility can cause
to the Next Steps in Signaling (NSIS) protocol suite, and shows how

RFC 5979 on NSIS Operation over IP Tunnels

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5979

        Title:      NSIS Operation over IP Tunnels 
        Author:     C. Shen, H. Schulzrinne,
                    S. Lee, J. Bang
        Status:     Experimental
        Stream:     IETF
        Date:       March 2011
        Mailbox:    charles <at> cs.columbia.edu, 
                    hgs <at> cs.columbia.edu, 
                    sung1.lee <at> samsung.com,  
                    jh0278.bang <at> samsung.com
        Pages:      27
        Characters: 69850
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nsis-tunnel-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5979.txt

NSIS Quality of Service (QoS) signaling enables applications to
perform QoS reservation along a data flow path.  When the data flow
path contains IP tunnel segments, NSIS QoS signaling has no effect
within those tunnel segments.  Therefore, the resulting tunnel
segments could become the weakest QoS link and invalidate the QoS
efforts in the rest of the end-to-end path.  The problem with NSIS

Errata 977 for RFC 4230

The errata 977 for RFC 4230 (http://www.rfc-editor.org/errata_search.php?eid=977) seems to be
correct, in the sense that the figure 1 is not explicitly saying RSVP INTEGRITY object. 

However, this can be fixed in a possible revision of RFC 4230, meaning that the proposed action for this
errata is "Hold for Document Update".  The proposed fixed would be to replace the standalone "object" in
figure 1 with " RSVP INTEGRITY object". 

Please send any comment to the nsis list until Feb 23 COB PT.

The text from the errata 977:

Section 3.4 says:

        [...].  The RSVP INTEGRITY object (outer object) covers the
   entire RSVP message, whereas the POLICY_DATA INTEGRITY object only
   covers objects within the POLICY_DATA element.

It should say:

[not submitted]

Notes:

The subsequent Figure 1 (on top of page 10)
does *not* depict this security relevant object at all.

Has there something been fost from Figure 1 ?

from pending

Errata 976 for RFC 4230

The errata 976 for RFC 4230 (http://www.rfc-editor.org/errata_search.php?eid=976) seems to be correct:

Section 3.2 says:

   The sending system needs to maintain the following attributes in such
   a security association [1]:

      [...]

      o  Latest sequence number (received with this key identifier)
                                 ^^^^^^^^

It should say:

   The sending system needs to maintain the following attributes in such
   a security association [1]:

     [...]

      o  Latest sequence number (sent with this key identifier)
                                 ^^^^

Any objection to the proposed fix?

The proposed action for this errata is "Hold for Document Update"

Please send any comment to the nsis list until Feb 23 COB PT.

 Martin

WG update

Hi,

you have probably seen that draft-ietf-nsis-tunnel has completed its second ITF last call and IESG
approval and is now back with the RFC Editor. (As is
draft-ietf-nsis-applicability-mobility-signaling, which we held back due to its reference to draft-ietf-nsis-tunnel.)

The RFC Editor is waiting for three of the four authors of draft-ietf-nsis-tunnel to respond to their
AUTH48 questions.

As soon as the authors respond, the RFCs can be published and the NSIS WG will close.

Lars

_______________________________________________
nsis mailing list
nsis <at> ietf.org
https://www.ietf.org/mailman/listinfo/nsis

errata handling for NSIS related RFCs

Dear all, 

We have 2 errata for
> | RFC4230 |       976 | 2007-05-16     | Alfred Hoenes   | nsis     |
> Technical |
> | RFC4230 |       977 | 2007-05-16     | Alfred Hoenes   | nsis     |
> Technical |

The authors of RFC 4320 and the working group is asked to give their
feedback about these errata, i.e., if they are valid and if/how they can be
fixed. 

Please provide any feedback until Feb 14th COB.

Thanks

  Martin

> -----Original Message-----
> From: Eggert Lars [mailto:lars.eggert <at> nokia.com]
> Sent: Tuesday, January 25, 2011 6:30 AM
> To: tsv-chairs <at> ietf.org
> Subject: errata handling for TSV RFCs
> Importance: High
> 
> Hi,
> 
> please process your errata! See the table at the end of this email. The
> list is long esp. for NFSv4, TCPM and TSVWG.
> 

RFC 6084 on General Internet Signaling Transport (GIST) over Stream Control Transmission Protocol (SCTP) and Datagram Transport Layer Security (DTLS)

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6084

        Title:      General Internet Signaling Transport (GIST) 
                    over Stream Control Transmission Protocol (SCTP) 
                    and Datagram Transport Layer Security (DTLS) 
        Author:     X. Fu, C. Dickmann,
                    J. Crowcroft
        Status:     Experimental
        Stream:     IETF
        Date:       January 2011
        Mailbox:    fu <at> cs.uni-goettingen.de, 
                    mail <at> christian-dickmann.de, 
                    jon.crowcroft <at> cl.cam.ac.uk
        Pages:      12
        Characters: 27040
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nsis-ntlp-sctp-15.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6084.txt

The General Internet Signaling Transport (GIST) protocol currently
uses TCP or Transport Layer Security (TLS) over TCP for Connection
mode operation.  This document describes the usage of GIST over the
Stream Control Transmission Protocol (SCTP) and Datagram Transport
Layer Security (DTLS).  This document defines an Experimental Protocol

Last Call: <draft-ietf-nsis-tunnel-13.txt> (NSIS Operation Over IP Tunnels) to Experimental RFC

The IESG has received a request from the Next Steps in Signaling WG
(nsis) to consider the following document:
- 'NSIS Operation Over IP Tunnels'
  <draft-ietf-nsis-tunnel-13.txt> as an Experimental RFC

This is the second IETF last call for this document. It had previously been last called
(http://www.ietf.org/mail-archive/web/ietf-announce/current/msg07553.html) and approved by
the IESG (http://www.ietf.org/mail-archive/web/ietf-announce/current/msg07730.html), but a
very late IPR disclosure (https://datatracker.ietf.org/ipr/1461/) arrived during RFC Editor
processing. Taking this disclosure into account, the WG has reconfirmed their consensus to publish this
document. The purpose of this second IETF last call is to reconfirm the consensus of the IETF at large.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf <at> ietf.org mailing lists by 2011-01-27. Exceptionally, comments may be
sent to iesg <at> ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-nsis-tunnel/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-nsis-tunnel/

The following IPR Declarations may be related to this I-D:

/ipr/1456/
/ipr/1461/