Revised SAP draft submitted
Colin Perkins <C.Perkins@cs.ucl.ac.uk> Thu, 24 February 2000 16:46 UTC
Return-Path: <owner-confctrl>
Received: (from majordom@localhost) by zephyr.isi.edu (8.8.7/8.8.6) id IAA29940 for confctrl-outgoing; Thu, 24 Feb 2000 08:46:03 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id IAA29929 for <confctrl@zephyr.isi.edu>; Thu, 24 Feb 2000 08:46:01 -0800 (PST)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by tnt.isi.edu (8.8.7/8.8.6) with SMTP id IAA16030 for <confctrl@isi.edu>; Thu, 24 Feb 2000 08:46:02 -0800 (PST)
Received: from eucharisto.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id <g.12923-0@bells.cs.ucl.ac.uk>; Thu, 24 Feb 2000 16:45:15 +0000
To: confctrl@ISI.EDU
Subject: Revised SAP draft submitted
Date: Thu, 24 Feb 2000 16:45:15 +0000
Message-ID: <2620.951410715@cs.ucl.ac.uk>
From: Colin Perkins <C.Perkins@cs.ucl.ac.uk>
Sender: owner-confctrl@zephyr.isi.edu
Precedence: bulk
I've just submitted a revision to the session announcement protocol draft, which addresses the comments I received during working group last call. Until it appears in the internet-draft archives, the draft is available from: http://www.cs.ucl.ac.uk/staff/c.perkins/internet-drafts/draft-ietf-mmusic-sap-v2-05.txt Summary of changes since the -04 revision: - Remove references to "client" in the text, now talks about SAP announcers and listeners only. - Clarify that TTL scoping is discouraged (in favour of admin scoping) - Clarify section on session deletion - Remove the optional timeout field from the packet format - It was only used for encrypted SAP, for those cases where a proxy didn't have the decryption key. - We now rely on either 1) the receiver of an announcement understands the payload, and can derive the session timeout from that (this is the common case) or 2) the announcer sends explicit deletion packets when it stops sending the announcement or 3) the receiver will timeout an announcement which hasn't been heard for some time (proxies which deal with encrypted SAP can still recognize cases 2 and 3). - Clarify why IPsec is not recommended for authentication. - Update references Colin
- Revised SAP draft submitted Colin Perkins
- Re: Revised SAP draft submitted Dave Thaler
- Re: Revised SAP draft submitted Peter T. Kirstein
- Re: Revised SAP draft submitted Mark Handley
- Re: Revised SAP draft submitted Dave Thaler
- Re: Revised SAP draft submitted Mark Handley
- Re: Revised SAP draft submitted Colin Perkins
- Re: Revised SAP draft submitted Peter KIRSTEIN