Hi, If "removing a binding" = "removing a flow", then I guess it's ok. REgards, Christer
________________________________ From: Francois Audet [mailto:[EMAIL PROTECTED] Sent: Fri 06/06/2008 18:39 To: Christer Holmberg; Dean Willis; [email protected] Cc: Cullen Jennings; Rohan Mahy Subject: RE: [Sip] What's happening with Outbound? I propose that we use the exact terminology of RFC 3261 (10.2.1 -adding-, 10.2.3 -removing- and 10.2.4 -refreshing). So it would look like this: Registrations for refreshing a binding and for removing a binding use the same instance-id and reg-id values as the corresponding initial registration where the binding was added. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Christer Holmberg > Sent: Thursday, June 05, 2008 20:04 > To: Dean Willis; [email protected] > Subject: Re: [Sip] What's happening with Outbound? > > Hi, > > One minor editorial issue: > > Chapter 4.2.2 says: > > "Re-registrations and single Contact de-registrations use the > same instance-id and reg-id values as the corresponding > initial registration." > > Other than the "Contact de-registrations" wording, I can't > find any text about explicitly removing flows (using REGISTER > with "0" expiration interval). Would it be possible to add > some extra words about that? > > Maybe simply saying: > > "Re-registrations and single Contact de-registrations (i.e. > explicit removal of flows) use the same..." > > Regards, > > Christer > > ________________________________ > > From: [EMAIL PROTECTED] on behalf of Dean Willis > Sent: Thu 05/06/2008 23:34 > To: [email protected] > Subject: [Sip] What's happening with Outbound? > > > > > We found a couple of typos and other nits in draft-ietf-sip- > outbound-14. The authors are working on a -15 that I expect > to be "final", so if you have any other changes you want in > there, get them to the list NOW. > > -- > Dean > > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol Use > [EMAIL PROTECTED] for questions on current sip > Use [EMAIL PROTECTED] for new developments on the application of sip > > > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol Use > [EMAIL PROTECTED] for questions on current sip > Use [EMAIL PROTECTED] for new developments on the application of sip > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
