Re: [Insipid] Adoption as WG item of draft-dawes-insipid-logme-marking

Hello All,
http://www.ietf.org/internet-drafts/draft-ietf-insipid-logme-marking-01.txt is now uploaded with an expanded clause 5.8 to differentiate B2BUA behaviour by B2BUA type as per RFC 7092. Thanks to Paul for pointing out the B2BUA taxonomy. 
As far as I know version -01 takes into account all comments so far but I would be happy to hear feedback on the revised clause 5.8 or any other part of the draft.

Regards,
Peter

-----Original Message-----
From: Dawes, Peter, Vodafone Group 
Sent: 19 August 2014 12:13
To: 'Gonzalo Salgueiro (gsalguei)'; insipid@ietf.org
Cc: insipid-chairs@tools.ietf.org
Subject: RE: [Insipid] Adoption as WG item of draft-dawes-insipid-logme-marking

Thanks Gonzalo and Keith,
http://www.ietf.org/internet-drafts/draft-ietf-insipid-logme-marking-00.txt is now uploaded. Thanks to Paul for his comments (see e-mail below), as a result I have edited Fig. 4 to correct the long lines and I will look into making sure that all B2BUA behaviour is fully described. 

Regards,
Peter

-----Original Message-----
From: insipid [mailto:insipid-bounces@ietf.org] On Behalf Of Paul Kyzivat
Sent: 11 July 2014 22:04
To: insipid@ietf.org
Subject: Re: [Insipid] draft-dawes-insipid-logme-marking-00

Just a couple of comments:

General comment: Run IdNits on this. You at least have lines that are too long.

Section 5.7.2. (B2BUA Processing of Log-Me Marker):

ISTM that not all B2BUAs should act the same way:

- SBC-like B2BUAs will most likely want to forward the logme marker from the incoming dialog to the corresponding outgoing dialog.

- more specialized B2BUAs may not want to do that. E.g., a conference focus may not want to forward incoming logme markers to all the other participant dialogs.

STRAW has a B2BUA taxonomy that might be useful to you for sorting this out.

	Thanks,
	Paul

-----Original Message-----
From: insipid [mailto:insipid-bounces@ietf.org] On Behalf Of Gonzalo Salgueiro (gsalguei)
Sent: 18 August 2014 19:01
To: insipid@ietf.org
Cc: insipid-chairs@tools.ietf.org
Subject: Re: [Insipid] Adoption as WG item of draft-dawes-insipid-logme-marking

The WG adoption call ended as scheduled and there is clear consensus from the WG in support of adoption of this document to satisfy our existing milestone (chairs noted strong acceptance and no objections).

The author should submit draft-ietf-*-00 version of the document as soon as possible.

Thanks,

Gonzalo and Keith
(as co-chairs)

--Sandy, speaking as wg co-chairs
On Aug 11, 2014, at 3:33 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:

> Support I do, Mr co-Chair.
> 
> Regards,
> 
> Christer
> 
> -----Original Message-----
> From: insipid [mailto:insipid-bounces@ietf.org] On Behalf Of DRAGE, 
> Keith (Keith)
> Sent: 06 August 2014 13:18
> To: DRAGE, Keith (Keith); insipid@ietf.org
> Subject: Re: [Insipid] Adoption as WG item of 
> draft-dawes-insipid-logme-marking
> 
> A reminder for people to respond by the 15th if they have an opinion on this.
> 
> Keith
> 
>> -----Original Message-----
>> From: DRAGE, Keith (Keith)
>> Sent: 24 July 2014 16:47
>> To: insipid@ietf.org
>> Subject: Adoption as WG item of draft-dawes-insipid-logme-marking
>> 
>> (as WG cochair)
>> 
>> We have a draft solutions document for the logme marking in:
>> 
>> http://www.ietf.org/id/draft-dawes-insipid-logme-marking-00.txt
>> 
>> No other documents have been identified to fulfil this work.
>> 
>> This is a call to adopt this text (or parts of it if
>> necessary) as text for the WG item.
>> 
>> Please respond by August 15th as to whether the text is acceptable to 
>> adopt and work on as WG text, or not.
>> 
>> If you consider only part of the text should be adopted, then please 
>> say so, and be specific as to what text is acceptable and what is not.
>> 
>> Regards
>> 
>> Keith
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
> 
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid

_______________________________________________
insipid mailing list
insipid@ietf.org
https://www.ietf.org/mailman/listinfo/insipid