
From HKaplan@acmepacket.com  Thu Dec  1 07:28:56 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1B5F11E8231 for <siprec@ietfa.amsl.com>; Thu,  1 Dec 2011 07:28:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9dinVdCTnm-E for <siprec@ietfa.amsl.com>; Thu,  1 Dec 2011 07:28:56 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id B8A7111E8198 for <siprec@ietf.org>; Thu,  1 Dec 2011 07:28:55 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 1 Dec 2011 10:28:54 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.245]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Thu, 1 Dec 2011 10:28:54 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [siprec] Transport of snapshot request
Thread-Index: AQHMsD3uOK/CoKcFIkS5/zLNxXgC8w==
Date: Thu, 1 Dec 2011 15:28:53 +0000
Message-ID: <AB722865-2E55-4184-86A5-288B344B650C@acmepacket.com>
References: <B20359D2613947B69891A631964F8457@JohnsComputer> <6ACE27C1-E11E-4137-A0E9-81BDF6C0E524@gmail.com> <622B0E14298DDE47ACA9E16B292F22A40F2F7EB2@Mail1.acmepacket.com> <387F9047F55E8C42850AD6B3A7A03C6C01D9D17E@inba-mail02.sonusnet.com> <4ED6EAA3.6060708@alum.mit.edu>
In-Reply-To: <4ED6EAA3.6060708@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.0.0.30]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C8556DFA70F7CF459E596624CC970021@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<siprec@ietf.org>" <siprec@ietf.org>
Subject: Re: [siprec] Transport of snapshot request
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Dec 2011 15:28:56 -0000

The reason to "exclude" anything is to improve interoperability.  I've seen=
 countless issues with implementations not expecting another device to do s=
omething causing problems when the other device does it, and definitely for=
 re-INVITEs and UPDATE scenarios.

So unless there's some pressing need to support multiple possible scenarios=
, I don't see any reason not to just pick one and only one way to do someth=
ing - it will improve interop to do so.

If we think a snapshot request from the SRS will usually need SDP from the =
SRC, and we don't think the SRS can provide an SDP offer in the snapshot re=
quest - and I don't think the SRS can in fact always provide an SDP offer i=
n it because the whole reason it's asking for a snapshot is it forgot stuff=
 - then we should pick a way to do it without requiring the SRS to send an =
SDP offer.

Ergo, I vote we pick the snapshot request mechanism be an offerless re-INVI=
TE, period.  That will work in every scenario anyone has ever mentioned, af=
aict, and thus there's no reason to do anything else.  No?

-hadriel


On Nov 30, 2011, at 9:46 PM, Paul Kyzivat wrote:

> On 12/1/11 8:47 AM, Ravindran, Parthasarathi wrote:
>> Hi all,
>>=20
>> I agree with UPDATE without SDP based snapshot request in case there is
>> an agreement that SRS will never generate offer as there is no possibili=
ty
>> of offer-answer race condition based on snapshot request mechanism. So,
>> I'm interested in hearing everybody opinion on "no offer from SRS" stanc=
e
>> For SIPREC.
>=20
> I don't see how it would ever make sense for the SRS to make an offer to =
the SRC, so I'm fine with declaring that invalid SRS behavior.
>=20
> As far as a snapshot without SDP, I agree it is unlikely that a snapshot =
would not require an SDP update. But I see no reason to exclude it in the u=
nlikely event that a case comes up when it is valid.
>=20
> This would be a problem if a snapshot request was in an UPDATE without SD=
P and the snapshot was required to be in the reply. But as long as the SRC =
can wait and send the snapshot in a request it initiates, it can make any o=
ffer it needs to, or potentially it could do the snapshot in an UPDATE with=
out SDP if no SDP was needed.
>=20
> 	Thanks,
> 	Paul
>=20
>> Brad/John,
>>=20
>> Please read inline.
>>=20
>> Thanks
>> Partha
>>=20
>>> -----Original Message-----
>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behal=
f
>>> Of Brad Winslow
>>> Sent: Wednesday, November 23, 2011 10:23 PM
>>> To: siprec@ietf.org
>>> Subject: Re: [siprec] Transport of snapshot request
>>>=20
>>> Hi Folks,
>>>=20
>>> In the situation where the SRS needs a metadata update, it most likely
>>> will need an SDP update, as there is no guarantee the metadata-only
>>> update would be consistent with the current SDP label attributes of the
>>> SRS, aren't we asking for trouble if we allow a metadata-only update?
>> <partha>  Snapshot request UPDATE without SDP from SRS is used to trigge=
r
>> Metadata request in SRC using RE-INVITE or UPDATE method
>> </partha>
>>=20
>>> If we decide on a full update, metadata + SDP, should we settle on
>>> UPDATE or INVITE to transmit the update from SRC to SRS?
>> <partha>  We have common understanding here</partha>
>>=20
>>>=20
>>> As an aside, there is an expectation that the SRC behaves as a SIP UA,
>>> in this case it should be able to respond to an offer-less re-INVITE
>>> from the SRS and provide metadata and SDP in the response.
>>>=20
>> <partha>  offerless Re-INVITE with 100 + 200 response is currently consi=
dered
>> as alternative Proposal to UPDATE without SDP snapshot request</partha>
>>=20
>>> Finally, if the SRS receives an INVITE for a new recording session,
>>> should we have an error code response which indicates the SRS is not
>>> interested in recording the session, not as a failure status, just as a
>>> status to terminate the recording.
>>=20
>> <partha>  It will be negative response in case INVITE with require:sipre=
c is
>> not accepted using 200 OK right? Do we need the new server negative 5xx
>> response code for this policy decision?</partha>
>>=20
>> This presupposes the SRS may make
>>> policy decisions for recording.
>>>=20
>>> Thanks in advance for your thoughts,
>>> Brad
>>>=20
>>> -----Original Message-----
>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behal=
f
>>> Of Leon Portman
>>> Sent: Thursday, November 17, 2011 4:47 AM
>>> To: John Elwell
>>> Cc: siprec@ietf.org
>>> Subject: Re: [siprec] Transport of snapshot request
>>>=20
>>> John, Nice to have you back on the list.
>>>=20
>>> Actually discussion during IETF meeting was started to converge to
>>> similar as you describe below.
>>>=20
>>> Regards
>>>=20
>>> Leon
>>>=20
>>> On Nov 17, 2011, at 5:15 PM, John Elwell wrote:
>>>=20
>>>> There has been a long thread discussing the SIP messages for snapshot
>>> requests.
>>>>=20
>>>> First, I see no reason to tie the snapshot request and the metadata
>>> transmission to the same transaction (request/response). If they are
>>> tied together, this imposes unnecessary time and architectural
>>> constraints on the SRC.
>>=20
>> <partha>  The model proposed is request/provisional response/response
>> Wherein RE-INVITE/100/200 trying shall be used wherein there is no
>> Immediate response to SRS.</partha>
>>=20
>> I much prefer an approach similar to the
>>> subscribe/notify approach of RFC 3265 - use different transactions.
>>=20
>> <partha>  The downside of this approach is 4 SIP messages per every
>> Service. I'm seeing the middle ground of offerless RE-INVITE with
>> Provisional response (100) and final response wherein 3 messages are
>> Involved but there is no extra offer/answer race condition from SRS.
>>=20
>> Having said that, in case it is confirmed that SRS will never offer
>> Then I'm fine with UPDATE based snapshot request</partha>
>>=20
>>  I am
>>> rather unsympathetic to allowing, as an option, metadata transmission i=
n
>>> a response. Apart from the timing and architectural concerns, there is
>>> no means of responding to a response if anything is wrong. Keep it
>>> simple, and allow metadata transmission only in requests, as in NOTIFY.
>>>>=20
>>>> Second, I think it is an SRC decision whether it needs a further
>>> offer-answer exchange. When sending the request containing the metadata=
,
>>> the SRC must ensure that any references to media description labels are
>>> consistent with the last SDP sent by the SRC - if not, the SRC can
>>> initiate a further offer-answer exchange at the same time as the
>>> metadata transmission.
>>>>=20
>>>> Perhaps it is my imagination, but I thought we had on the table at one
>>> time the notion of:
>>>> - SRS sends snapshot request in an UPDATE request.
>>>> - SRC sends medata in an UPDATE request (with offer if it needs to
>>> change SDP, otherwise without).
>>>>=20
>>>> I have lost track of how we came to diverge from this simple model.
>>>>=20
>>>> John
>>>>=20
>>>> _______________________________________________
>>>> siprec mailing list
>>>> siprec@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>=20
>>> _______________________________________________
>>> siprec mailing list
>>> siprec@ietf.org
>>> https://www.ietf.org/mailman/listinfo/siprec
>>> _______________________________________________
>>> siprec mailing list
>>> siprec@ietf.org
>>> https://www.ietf.org/mailman/listinfo/siprec
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
>>=20
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec


From pkyzivat@alum.mit.edu  Thu Dec  1 10:27:33 2011
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D668D11E80F8 for <siprec@ietfa.amsl.com>; Thu,  1 Dec 2011 10:27:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZmTlqOp0qS6A for <siprec@ietfa.amsl.com>; Thu,  1 Dec 2011 10:27:32 -0800 (PST)
Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by ietfa.amsl.com (Postfix) with ESMTP id 8287911E80EB for <siprec@ietf.org>; Thu,  1 Dec 2011 10:27:29 -0800 (PST)
Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by qmta08.westchester.pa.mail.comcast.net with comcast id 3rVl1i00E1ZXKqc58uTVRY; Thu, 01 Dec 2011 18:27:29 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta21.westchester.pa.mail.comcast.net with comcast id 3uTV1i00T07duvL3huTVP7; Thu, 01 Dec 2011 18:27:29 +0000
Message-ID: <4ED7C70C.6050004@alum.mit.edu>
Date: Fri, 02 Dec 2011 02:27:24 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <B20359D2613947B69891A631964F8457@JohnsComputer> <6ACE27C1-E11E-4137-A0E9-81BDF6C0E524@gmail.com> <622B0E14298DDE47ACA9E16B292F22A40F2F7EB2@Mail1.acmepacket.com> <387F9047F55E8C42850AD6B3A7A03C6C01D9D17E@inba-mail02.sonusnet.com> <4ED6EAA3.6060708@alum.mit.edu> <AB722865-2E55-4184-86A5-288B344B650C@acmepacket.com>
In-Reply-To: <AB722865-2E55-4184-86A5-288B344B650C@acmepacket.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "<siprec@ietf.org>" <siprec@ietf.org>
Subject: Re: [siprec] Transport of snapshot request
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Dec 2011 18:27:33 -0000

On 12/1/11 11:28 PM, Hadriel Kaplan wrote:
>
> The reason to "exclude" anything is to improve interoperability.  I've seen countless issues with implementations not expecting another device to do something causing problems when the other device does it, and definitely for re-INVITEs and UPDATE scenarios.
>
> So unless there's some pressing need to support multiple possible scenarios, I don't see any reason not to just pick one and only one way to do something - it will improve interop to do so.
>
> If we think a snapshot request from the SRS will usually need SDP from the SRC, and we don't think the SRS can provide an SDP offer in the snapshot request - and I don't think the SRS can in fact always provide an SDP offer in it because the whole reason it's asking for a snapshot is it forgot stuff - then we should pick a way to do it without requiring the SRS to send an SDP offer.
>
> Ergo, I vote we pick the snapshot request mechanism be an offerless re-INVITE, period.  That will work in every scenario anyone has ever mentioned, afaict, and thus there's no reason to do anything else.  No?

I have a slightly different spin on this:

Send the snapshot is a different transaction from the snapshot request.
That allows the SRC to be in control of the o/a machinery. It also 
decouples the preparation of the snapshot from all the transaction 
timers - which is good from a layering perspective.

If we do that, then the sending of a snapshot isn't very different than 
sending an update - it just contains elements that would otherwise be 
skipped as redundant. And so it should be able to go into any signaling 
that a comparable update could go in.

We can discuss what sort of message the snapshot request should go in. 
The likely alternatives are an offerless re-INVITE or an offerless 
UPDATE. The UPDATE would be more optimal because then there will be no 
o/a at all with it. *If* the SRS has somehow forgotten the SDP, then an 
offerless re-INVITE would bring an offer with whatever the SRC thinks 
should be current, without metadata.

So then we get to the question of whether snapshots or updates can 
travel in UPDATE or if they must use INVITE. IMO both should be allowed, 
for two reasons:
- there can be common cases where you want to update metadata
   but there is no need to change the SDP. UPDATE is the easy way
   to accomplish this. It might not be the common choice for
   snapshots, but its an independent decision.

- the SRC "application" sitting on top of the stack may not have
   complete control over the sip stack. The stack will be dealing
   with the o/a behavior, and the application will be dealing with
   the metadata. It may not be so easy to control the decision of
   whether to use INVITE or UPDATE.

IMO the idea of requiring that things be done in one way, when the basic 
mechanisms allow multiple ways, is a dubious economy and a slippery 
slope. Its a dubious economy because it may require extra code to 
prevent alternatives from being used. And its a slippery slope because 
there are lots of other optional ways of doing things that could 
conceivably be proposed as "simplifications". E.g. ordering headers in a 
particular way, not using abbreviations for header names.

(Note it may be that a re-INVITE carrying metadata may end up also 
requiring an UPDATE. This would occur if preconditions are used in order 
to set up QoS on the media lines. I bring this up as an example of why 
the stack should be allowed to do what it needs to do.)

	Thanks,
	Paul

> -hadriel
>
>
> On Nov 30, 2011, at 9:46 PM, Paul Kyzivat wrote:
>
>> On 12/1/11 8:47 AM, Ravindran, Parthasarathi wrote:
>>> Hi all,
>>>
>>> I agree with UPDATE without SDP based snapshot request in case there is
>>> an agreement that SRS will never generate offer as there is no possibility
>>> of offer-answer race condition based on snapshot request mechanism. So,
>>> I'm interested in hearing everybody opinion on "no offer from SRS" stance
>>> For SIPREC.
>>
>> I don't see how it would ever make sense for the SRS to make an offer to the SRC, so I'm fine with declaring that invalid SRS behavior.
>>
>> As far as a snapshot without SDP, I agree it is unlikely that a snapshot would not require an SDP update. But I see no reason to exclude it in the unlikely event that a case comes up when it is valid.
>>
>> This would be a problem if a snapshot request was in an UPDATE without SDP and the snapshot was required to be in the reply. But as long as the SRC can wait and send the snapshot in a request it initiates, it can make any offer it needs to, or potentially it could do the snapshot in an UPDATE without SDP if no SDP was needed.
>>
>> 	Thanks,
>> 	Paul
>>
>>> Brad/John,
>>>
>>> Please read inline.
>>>
>>> Thanks
>>> Partha
>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>>>> Of Brad Winslow
>>>> Sent: Wednesday, November 23, 2011 10:23 PM
>>>> To: siprec@ietf.org
>>>> Subject: Re: [siprec] Transport of snapshot request
>>>>
>>>> Hi Folks,
>>>>
>>>> In the situation where the SRS needs a metadata update, it most likely
>>>> will need an SDP update, as there is no guarantee the metadata-only
>>>> update would be consistent with the current SDP label attributes of the
>>>> SRS, aren't we asking for trouble if we allow a metadata-only update?
>>> <partha>   Snapshot request UPDATE without SDP from SRS is used to trigger
>>> Metadata request in SRC using RE-INVITE or UPDATE method
>>> </partha>
>>>
>>>> If we decide on a full update, metadata + SDP, should we settle on
>>>> UPDATE or INVITE to transmit the update from SRC to SRS?
>>> <partha>   We have common understanding here</partha>
>>>
>>>>
>>>> As an aside, there is an expectation that the SRC behaves as a SIP UA,
>>>> in this case it should be able to respond to an offer-less re-INVITE
>>>> from the SRS and provide metadata and SDP in the response.
>>>>
>>> <partha>   offerless Re-INVITE with 100 + 200 response is currently considered
>>> as alternative Proposal to UPDATE without SDP snapshot request</partha>
>>>
>>>> Finally, if the SRS receives an INVITE for a new recording session,
>>>> should we have an error code response which indicates the SRS is not
>>>> interested in recording the session, not as a failure status, just as a
>>>> status to terminate the recording.
>>>
>>> <partha>   It will be negative response in case INVITE with require:siprec is
>>> not accepted using 200 OK right? Do we need the new server negative 5xx
>>> response code for this policy decision?</partha>
>>>
>>> This presupposes the SRS may make
>>>> policy decisions for recording.
>>>>
>>>> Thanks in advance for your thoughts,
>>>> Brad
>>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf
>>>> Of Leon Portman
>>>> Sent: Thursday, November 17, 2011 4:47 AM
>>>> To: John Elwell
>>>> Cc: siprec@ietf.org
>>>> Subject: Re: [siprec] Transport of snapshot request
>>>>
>>>> John, Nice to have you back on the list.
>>>>
>>>> Actually discussion during IETF meeting was started to converge to
>>>> similar as you describe below.
>>>>
>>>> Regards
>>>>
>>>> Leon
>>>>
>>>> On Nov 17, 2011, at 5:15 PM, John Elwell wrote:
>>>>
>>>>> There has been a long thread discussing the SIP messages for snapshot
>>>> requests.
>>>>>
>>>>> First, I see no reason to tie the snapshot request and the metadata
>>>> transmission to the same transaction (request/response). If they are
>>>> tied together, this imposes unnecessary time and architectural
>>>> constraints on the SRC.
>>>
>>> <partha>   The model proposed is request/provisional response/response
>>> Wherein RE-INVITE/100/200 trying shall be used wherein there is no
>>> Immediate response to SRS.</partha>
>>>
>>> I much prefer an approach similar to the
>>>> subscribe/notify approach of RFC 3265 - use different transactions.
>>>
>>> <partha>   The downside of this approach is 4 SIP messages per every
>>> Service. I'm seeing the middle ground of offerless RE-INVITE with
>>> Provisional response (100) and final response wherein 3 messages are
>>> Involved but there is no extra offer/answer race condition from SRS.
>>>
>>> Having said that, in case it is confirmed that SRS will never offer
>>> Then I'm fine with UPDATE based snapshot request</partha>
>>>
>>>   I am
>>>> rather unsympathetic to allowing, as an option, metadata transmission in
>>>> a response. Apart from the timing and architectural concerns, there is
>>>> no means of responding to a response if anything is wrong. Keep it
>>>> simple, and allow metadata transmission only in requests, as in NOTIFY.
>>>>>
>>>>> Second, I think it is an SRC decision whether it needs a further
>>>> offer-answer exchange. When sending the request containing the metadata,
>>>> the SRC must ensure that any references to media description labels are
>>>> consistent with the last SDP sent by the SRC - if not, the SRC can
>>>> initiate a further offer-answer exchange at the same time as the
>>>> metadata transmission.
>>>>>
>>>>> Perhaps it is my imagination, but I thought we had on the table at one
>>>> time the notion of:
>>>>> - SRS sends snapshot request in an UPDATE request.
>>>>> - SRC sends medata in an UPDATE request (with offer if it needs to
>>>> change SDP, otherwise without).
>>>>>
>>>>> I have lost track of how we came to diverge from this simple model.
>>>>>
>>>>> John
>>>>>
>>>>> _______________________________________________
>>>>> siprec mailing list
>>>>> siprec@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>
>>>> _______________________________________________
>>>> siprec mailing list
>>>> siprec@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>> _______________________________________________
>>>> siprec mailing list
>>>> siprec@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/siprec
>>> _______________________________________________
>>> siprec mailing list
>>> siprec@ietf.org
>>> https://www.ietf.org/mailman/listinfo/siprec
>>>
>>
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
>
>


From eckelcu@cisco.com  Thu Dec  1 10:56:40 2011
Return-Path: <eckelcu@cisco.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 744881F0C7C for <siprec@ietfa.amsl.com>; Thu,  1 Dec 2011 10:56:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bikr4NMO6+zQ for <siprec@ietfa.amsl.com>; Thu,  1 Dec 2011 10:56:39 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 311481F0C4B for <siprec@ietf.org>; Thu,  1 Dec 2011 10:56:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eckelcu@cisco.com; l=11621; q=dns/txt; s=iport; t=1322765799; x=1323975399; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=t3lg7Fx0/oDdr54WXw3O1QX3e1CmPzxZXDXSdTLZ1q8=; b=Sd6Sb1CXPhToaN6s7JitSkPnSFGpm+12nZBWu5M4NsmbzIsmSI0NAam2 IkDHtJM7w5niAfNsZaFgyklf0BRPuIh3l1eGGefGPVM8GmhKTWju4Dfhh JUHig+ywoxoI+vO+IiacwiwesBpVHxp6YyX+vrwgRcYBBWvK5rZ8VjQQo E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqMAAH7N106rRDoJ/2dsb2JhbABEDppIkCOBBYFyAQEBBAEBAQ8BHQo0CwwEAgEIDgMEAQEBCgIEFwEGASYfCQgBAQQBEggah22ZNAGeRQSKPWMEiCieClg
X-IronPort-AV: E=Sophos;i="4.71,279,1320624000"; d="scan'208";a="15516495"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 01 Dec 2011 18:56:38 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pB1IucHC014404; Thu, 1 Dec 2011 18:56:38 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Dec 2011 10:56:38 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 1 Dec 2011 10:56:36 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05D81F53@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <4ED7C70C.6050004@alum.mit.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [siprec] Transport of snapshot request
Thread-Index: AcywVumNUZmzAER9S86wfXQ1zr/lsAAA5yVw
References: <B20359D2613947B69891A631964F8457@JohnsComputer><6ACE27C1-E11E-4137-A0E9-81BDF6C0E524@gmail.com><622B0E14298DDE47ACA9E16B292F22A40F2F7EB2@Mail1.acmepacket.com><387F9047F55E8C42850AD6B3A7A03C6C01D9D17E@inba-mail02.sonusnet.com><4ED6EAA3.6060708@alum.mit.edu><AB722865-2E55-4184-86A5-288B344B650C@acmepacket.com> <4ED7C70C.6050004@alum.mit.edu>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Paul Kyzivat" <pkyzivat@alum.mit.edu>, "Hadriel Kaplan" <HKaplan@acmepacket.com>
X-OriginalArrivalTime: 01 Dec 2011 18:56:38.0596 (UTC) FILETIME=[F4B52840:01CCB05A]
Cc: siprec@ietf.org
Subject: Re: [siprec] Transport of snapshot request
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Dec 2011 18:56:40 -0000

Hi Paul,

If we go with this approach, then in the case of the SRS sending an
offer-less INVITE requesting a snapshot, it would also be valid for the
SRC to respond with an offer + metadata snapshot, correct?=20

Charles

> -----Original Message-----
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf Of Paul Kyzivat
> Sent: Thursday, December 01, 2011 10:27 AM
> To: Hadriel Kaplan
> Cc: <siprec@ietf.org>
> Subject: Re: [siprec] Transport of snapshot request
>=20
> On 12/1/11 11:28 PM, Hadriel Kaplan wrote:
> >
> > The reason to "exclude" anything is to improve interoperability.
I've seen countless issues with
> implementations not expecting another device to do something causing
problems when the other device
> does it, and definitely for re-INVITEs and UPDATE scenarios.
> >
> > So unless there's some pressing need to support multiple possible
scenarios, I don't see any reason
> not to just pick one and only one way to do something - it will
improve interop to do so.
> >
> > If we think a snapshot request from the SRS will usually need SDP
from the SRC, and we don't think
> the SRS can provide an SDP offer in the snapshot request - and I don't
think the SRS can in fact
> always provide an SDP offer in it because the whole reason it's asking
for a snapshot is it forgot
> stuff - then we should pick a way to do it without requiring the SRS
to send an SDP offer.
> >
> > Ergo, I vote we pick the snapshot request mechanism be an offerless
re-INVITE, period.  That will
> work in every scenario anyone has ever mentioned, afaict, and thus
there's no reason to do anything
> else.  No?
>=20
> I have a slightly different spin on this:
>=20
> Send the snapshot is a different transaction from the snapshot
request.
> That allows the SRC to be in control of the o/a machinery. It also
> decouples the preparation of the snapshot from all the transaction
> timers - which is good from a layering perspective.
>=20
> If we do that, then the sending of a snapshot isn't very different
than
> sending an update - it just contains elements that would otherwise be
> skipped as redundant. And so it should be able to go into any
signaling
> that a comparable update could go in.
>=20
> We can discuss what sort of message the snapshot request should go in.
> The likely alternatives are an offerless re-INVITE or an offerless
> UPDATE. The UPDATE would be more optimal because then there will be no
> o/a at all with it. *If* the SRS has somehow forgotten the SDP, then
an
> offerless re-INVITE would bring an offer with whatever the SRC thinks
> should be current, without metadata.
>=20
> So then we get to the question of whether snapshots or updates can
> travel in UPDATE or if they must use INVITE. IMO both should be
allowed,
> for two reasons:
> - there can be common cases where you want to update metadata
>    but there is no need to change the SDP. UPDATE is the easy way
>    to accomplish this. It might not be the common choice for
>    snapshots, but its an independent decision.
>=20
> - the SRC "application" sitting on top of the stack may not have
>    complete control over the sip stack. The stack will be dealing
>    with the o/a behavior, and the application will be dealing with
>    the metadata. It may not be so easy to control the decision of
>    whether to use INVITE or UPDATE.
>=20
> IMO the idea of requiring that things be done in one way, when the
basic
> mechanisms allow multiple ways, is a dubious economy and a slippery
> slope. Its a dubious economy because it may require extra code to
> prevent alternatives from being used. And its a slippery slope because
> there are lots of other optional ways of doing things that could
> conceivably be proposed as "simplifications". E.g. ordering headers in
a
> particular way, not using abbreviations for header names.
>=20
> (Note it may be that a re-INVITE carrying metadata may end up also
> requiring an UPDATE. This would occur if preconditions are used in
order
> to set up QoS on the media lines. I bring this up as an example of why
> the stack should be allowed to do what it needs to do.)
>=20
> 	Thanks,
> 	Paul
>=20
> > -hadriel
> >
> >
> > On Nov 30, 2011, at 9:46 PM, Paul Kyzivat wrote:
> >
> >> On 12/1/11 8:47 AM, Ravindran, Parthasarathi wrote:
> >>> Hi all,
> >>>
> >>> I agree with UPDATE without SDP based snapshot request in case
there is
> >>> an agreement that SRS will never generate offer as there is no
possibility
> >>> of offer-answer race condition based on snapshot request
mechanism. So,
> >>> I'm interested in hearing everybody opinion on "no offer from SRS"
stance
> >>> For SIPREC.
> >>
> >> I don't see how it would ever make sense for the SRS to make an
offer to the SRC, so I'm fine with
> declaring that invalid SRS behavior.
> >>
> >> As far as a snapshot without SDP, I agree it is unlikely that a
snapshot would not require an SDP
> update. But I see no reason to exclude it in the unlikely event that a
case comes up when it is valid.
> >>
> >> This would be a problem if a snapshot request was in an UPDATE
without SDP and the snapshot was
> required to be in the reply. But as long as the SRC can wait and send
the snapshot in a request it
> initiates, it can make any offer it needs to, or potentially it could
do the snapshot in an UPDATE
> without SDP if no SDP was needed.
> >>
> >> 	Thanks,
> >> 	Paul
> >>
> >>> Brad/John,
> >>>
> >>> Please read inline.
> >>>
> >>> Thanks
> >>> Partha
> >>>
> >>>> -----Original Message-----
> >>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf
> >>>> Of Brad Winslow
> >>>> Sent: Wednesday, November 23, 2011 10:23 PM
> >>>> To: siprec@ietf.org
> >>>> Subject: Re: [siprec] Transport of snapshot request
> >>>>
> >>>> Hi Folks,
> >>>>
> >>>> In the situation where the SRS needs a metadata update, it most
likely
> >>>> will need an SDP update, as there is no guarantee the
metadata-only
> >>>> update would be consistent with the current SDP label attributes
of the
> >>>> SRS, aren't we asking for trouble if we allow a metadata-only
update?
> >>> <partha>   Snapshot request UPDATE without SDP from SRS is used to
trigger
> >>> Metadata request in SRC using RE-INVITE or UPDATE method
> >>> </partha>
> >>>
> >>>> If we decide on a full update, metadata + SDP, should we settle
on
> >>>> UPDATE or INVITE to transmit the update from SRC to SRS?
> >>> <partha>   We have common understanding here</partha>
> >>>
> >>>>
> >>>> As an aside, there is an expectation that the SRC behaves as a
SIP UA,
> >>>> in this case it should be able to respond to an offer-less
re-INVITE
> >>>> from the SRS and provide metadata and SDP in the response.
> >>>>
> >>> <partha>   offerless Re-INVITE with 100 + 200 response is
currently considered
> >>> as alternative Proposal to UPDATE without SDP snapshot
request</partha>
> >>>
> >>>> Finally, if the SRS receives an INVITE for a new recording
session,
> >>>> should we have an error code response which indicates the SRS is
not
> >>>> interested in recording the session, not as a failure status,
just as a
> >>>> status to terminate the recording.
> >>>
> >>> <partha>   It will be negative response in case INVITE with
require:siprec is
> >>> not accepted using 200 OK right? Do we need the new server
negative 5xx
> >>> response code for this policy decision?</partha>
> >>>
> >>> This presupposes the SRS may make
> >>>> policy decisions for recording.
> >>>>
> >>>> Thanks in advance for your thoughts,
> >>>> Brad
> >>>>
> >>>> -----Original Message-----
> >>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
Behalf
> >>>> Of Leon Portman
> >>>> Sent: Thursday, November 17, 2011 4:47 AM
> >>>> To: John Elwell
> >>>> Cc: siprec@ietf.org
> >>>> Subject: Re: [siprec] Transport of snapshot request
> >>>>
> >>>> John, Nice to have you back on the list.
> >>>>
> >>>> Actually discussion during IETF meeting was started to converge
to
> >>>> similar as you describe below.
> >>>>
> >>>> Regards
> >>>>
> >>>> Leon
> >>>>
> >>>> On Nov 17, 2011, at 5:15 PM, John Elwell wrote:
> >>>>
> >>>>> There has been a long thread discussing the SIP messages for
snapshot
> >>>> requests.
> >>>>>
> >>>>> First, I see no reason to tie the snapshot request and the
metadata
> >>>> transmission to the same transaction (request/response). If they
are
> >>>> tied together, this imposes unnecessary time and architectural
> >>>> constraints on the SRC.
> >>>
> >>> <partha>   The model proposed is request/provisional
response/response
> >>> Wherein RE-INVITE/100/200 trying shall be used wherein there is no
> >>> Immediate response to SRS.</partha>
> >>>
> >>> I much prefer an approach similar to the
> >>>> subscribe/notify approach of RFC 3265 - use different
transactions.
> >>>
> >>> <partha>   The downside of this approach is 4 SIP messages per
every
> >>> Service. I'm seeing the middle ground of offerless RE-INVITE with
> >>> Provisional response (100) and final response wherein 3 messages
are
> >>> Involved but there is no extra offer/answer race condition from
SRS.
> >>>
> >>> Having said that, in case it is confirmed that SRS will never
offer
> >>> Then I'm fine with UPDATE based snapshot request</partha>
> >>>
> >>>   I am
> >>>> rather unsympathetic to allowing, as an option, metadata
transmission in
> >>>> a response. Apart from the timing and architectural concerns,
there is
> >>>> no means of responding to a response if anything is wrong. Keep
it
> >>>> simple, and allow metadata transmission only in requests, as in
NOTIFY.
> >>>>>
> >>>>> Second, I think it is an SRC decision whether it needs a further
> >>>> offer-answer exchange. When sending the request containing the
metadata,
> >>>> the SRC must ensure that any references to media description
labels are
> >>>> consistent with the last SDP sent by the SRC - if not, the SRC
can
> >>>> initiate a further offer-answer exchange at the same time as the
> >>>> metadata transmission.
> >>>>>
> >>>>> Perhaps it is my imagination, but I thought we had on the table
at one
> >>>> time the notion of:
> >>>>> - SRS sends snapshot request in an UPDATE request.
> >>>>> - SRC sends medata in an UPDATE request (with offer if it needs
to
> >>>> change SDP, otherwise without).
> >>>>>
> >>>>> I have lost track of how we came to diverge from this simple
model.
> >>>>>
> >>>>> John
> >>>>>
> >>>>> _______________________________________________
> >>>>> siprec mailing list
> >>>>> siprec@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/siprec
> >>>>
> >>>> _______________________________________________
> >>>> siprec mailing list
> >>>> siprec@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/siprec
> >>>> _______________________________________________
> >>>> siprec mailing list
> >>>> siprec@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/siprec
> >>> _______________________________________________
> >>> siprec mailing list
> >>> siprec@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/siprec
> >>>
> >>
> >> _______________________________________________
> >> siprec mailing list
> >> siprec@ietf.org
> >> https://www.ietf.org/mailman/listinfo/siprec
> >
> >
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec

From pkyzivat@alum.mit.edu  Thu Dec  1 11:45:08 2011
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F7A021F916D for <siprec@ietfa.amsl.com>; Thu,  1 Dec 2011 11:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ZTkrejOMLDk for <siprec@ietfa.amsl.com>; Thu,  1 Dec 2011 11:45:06 -0800 (PST)
Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9E4EE21F90EB for <siprec@ietf.org>; Thu,  1 Dec 2011 11:45:01 -0800 (PST)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta10.westchester.pa.mail.comcast.net with comcast id 3ujs1i0061c6gX85Avl1q6; Thu, 01 Dec 2011 19:45:01 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta23.westchester.pa.mail.comcast.net with comcast id 3vl01i00t07duvL3jvl0EX; Thu, 01 Dec 2011 19:45:01 +0000
Message-ID: <4ED7D93B.6060004@alum.mit.edu>
Date: Fri, 02 Dec 2011 03:44:59 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
References: <B20359D2613947B69891A631964F8457@JohnsComputer><6ACE27C1-E11E-4137-A0E9-81BDF6C0E524@gmail.com><622B0E14298DDE47ACA9E16B292F22A40F2F7EB2@Mail1.acmepacket.com><387F9047F55E8C42850AD6B3A7A03C6C01D9D17E@inba-mail02.sonusnet.com><4ED6EAA3.6060708@alum.mit.edu><AB722865-2E55-4184-86A5-288B344B650C@acmepacket.com> <4ED7C70C.6050004@alum.mit.edu> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05D81F53@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C05D81F53@xmb-sjc-234.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: siprec@ietf.org
Subject: Re: [siprec] Transport of snapshot request
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Dec 2011 19:45:08 -0000

On 12/2/11 2:56 AM, Charles Eckel (eckelcu) wrote:
> Hi Paul,
>
> If we go with this approach, then in the case of the SRS sending an
> offer-less INVITE requesting a snapshot, it would also be valid for the
> SRC to respond with an offer + metadata snapshot, correct?

We should discuss this.
IMO we could allow (but not require) this.
Or we could forbid it.

I don't have a strong opinion either way.

	Thanks,
	Paul

> Charles
>
>> -----Original Message-----
>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf Of Paul Kyzivat
>> Sent: Thursday, December 01, 2011 10:27 AM
>> To: Hadriel Kaplan
>> Cc:<siprec@ietf.org>
>> Subject: Re: [siprec] Transport of snapshot request
>>
>> On 12/1/11 11:28 PM, Hadriel Kaplan wrote:
>>>
>>> The reason to "exclude" anything is to improve interoperability.
> I've seen countless issues with
>> implementations not expecting another device to do something causing
> problems when the other device
>> does it, and definitely for re-INVITEs and UPDATE scenarios.
>>>
>>> So unless there's some pressing need to support multiple possible
> scenarios, I don't see any reason
>> not to just pick one and only one way to do something - it will
> improve interop to do so.
>>>
>>> If we think a snapshot request from the SRS will usually need SDP
> from the SRC, and we don't think
>> the SRS can provide an SDP offer in the snapshot request - and I don't
> think the SRS can in fact
>> always provide an SDP offer in it because the whole reason it's asking
> for a snapshot is it forgot
>> stuff - then we should pick a way to do it without requiring the SRS
> to send an SDP offer.
>>>
>>> Ergo, I vote we pick the snapshot request mechanism be an offerless
> re-INVITE, period.  That will
>> work in every scenario anyone has ever mentioned, afaict, and thus
> there's no reason to do anything
>> else.  No?
>>
>> I have a slightly different spin on this:
>>
>> Send the snapshot is a different transaction from the snapshot
> request.
>> That allows the SRC to be in control of the o/a machinery. It also
>> decouples the preparation of the snapshot from all the transaction
>> timers - which is good from a layering perspective.
>>
>> If we do that, then the sending of a snapshot isn't very different
> than
>> sending an update - it just contains elements that would otherwise be
>> skipped as redundant. And so it should be able to go into any
> signaling
>> that a comparable update could go in.
>>
>> We can discuss what sort of message the snapshot request should go in.
>> The likely alternatives are an offerless re-INVITE or an offerless
>> UPDATE. The UPDATE would be more optimal because then there will be no
>> o/a at all with it. *If* the SRS has somehow forgotten the SDP, then
> an
>> offerless re-INVITE would bring an offer with whatever the SRC thinks
>> should be current, without metadata.
>>
>> So then we get to the question of whether snapshots or updates can
>> travel in UPDATE or if they must use INVITE. IMO both should be
> allowed,
>> for two reasons:
>> - there can be common cases where you want to update metadata
>>     but there is no need to change the SDP. UPDATE is the easy way
>>     to accomplish this. It might not be the common choice for
>>     snapshots, but its an independent decision.
>>
>> - the SRC "application" sitting on top of the stack may not have
>>     complete control over the sip stack. The stack will be dealing
>>     with the o/a behavior, and the application will be dealing with
>>     the metadata. It may not be so easy to control the decision of
>>     whether to use INVITE or UPDATE.
>>
>> IMO the idea of requiring that things be done in one way, when the
> basic
>> mechanisms allow multiple ways, is a dubious economy and a slippery
>> slope. Its a dubious economy because it may require extra code to
>> prevent alternatives from being used. And its a slippery slope because
>> there are lots of other optional ways of doing things that could
>> conceivably be proposed as "simplifications". E.g. ordering headers in
> a
>> particular way, not using abbreviations for header names.
>>
>> (Note it may be that a re-INVITE carrying metadata may end up also
>> requiring an UPDATE. This would occur if preconditions are used in
> order
>> to set up QoS on the media lines. I bring this up as an example of why
>> the stack should be allowed to do what it needs to do.)
>>
>> 	Thanks,
>> 	Paul
>>
>>> -hadriel
>>>
>>>
>>> On Nov 30, 2011, at 9:46 PM, Paul Kyzivat wrote:
>>>
>>>> On 12/1/11 8:47 AM, Ravindran, Parthasarathi wrote:
>>>>> Hi all,
>>>>>
>>>>> I agree with UPDATE without SDP based snapshot request in case
> there is
>>>>> an agreement that SRS will never generate offer as there is no
> possibility
>>>>> of offer-answer race condition based on snapshot request
> mechanism. So,
>>>>> I'm interested in hearing everybody opinion on "no offer from SRS"
> stance
>>>>> For SIPREC.
>>>>
>>>> I don't see how it would ever make sense for the SRS to make an
> offer to the SRC, so I'm fine with
>> declaring that invalid SRS behavior.
>>>>
>>>> As far as a snapshot without SDP, I agree it is unlikely that a
> snapshot would not require an SDP
>> update. But I see no reason to exclude it in the unlikely event that a
> case comes up when it is valid.
>>>>
>>>> This would be a problem if a snapshot request was in an UPDATE
> without SDP and the snapshot was
>> required to be in the reply. But as long as the SRC can wait and send
> the snapshot in a request it
>> initiates, it can make any offer it needs to, or potentially it could
> do the snapshot in an UPDATE
>> without SDP if no SDP was needed.
>>>>
>>>> 	Thanks,
>>>> 	Paul
>>>>
>>>>> Brad/John,
>>>>>
>>>>> Please read inline.
>>>>>
>>>>> Thanks
>>>>> Partha
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf
>>>>>> Of Brad Winslow
>>>>>> Sent: Wednesday, November 23, 2011 10:23 PM
>>>>>> To: siprec@ietf.org
>>>>>> Subject: Re: [siprec] Transport of snapshot request
>>>>>>
>>>>>> Hi Folks,
>>>>>>
>>>>>> In the situation where the SRS needs a metadata update, it most
> likely
>>>>>> will need an SDP update, as there is no guarantee the
> metadata-only
>>>>>> update would be consistent with the current SDP label attributes
> of the
>>>>>> SRS, aren't we asking for trouble if we allow a metadata-only
> update?
>>>>> <partha>    Snapshot request UPDATE without SDP from SRS is used to
> trigger
>>>>> Metadata request in SRC using RE-INVITE or UPDATE method
>>>>> </partha>
>>>>>
>>>>>> If we decide on a full update, metadata + SDP, should we settle
> on
>>>>>> UPDATE or INVITE to transmit the update from SRC to SRS?
>>>>> <partha>    We have common understanding here</partha>
>>>>>
>>>>>>
>>>>>> As an aside, there is an expectation that the SRC behaves as a
> SIP UA,
>>>>>> in this case it should be able to respond to an offer-less
> re-INVITE
>>>>>> from the SRS and provide metadata and SDP in the response.
>>>>>>
>>>>> <partha>    offerless Re-INVITE with 100 + 200 response is
> currently considered
>>>>> as alternative Proposal to UPDATE without SDP snapshot
> request</partha>
>>>>>
>>>>>> Finally, if the SRS receives an INVITE for a new recording
> session,
>>>>>> should we have an error code response which indicates the SRS is
> not
>>>>>> interested in recording the session, not as a failure status,
> just as a
>>>>>> status to terminate the recording.
>>>>>
>>>>> <partha>    It will be negative response in case INVITE with
> require:siprec is
>>>>> not accepted using 200 OK right? Do we need the new server
> negative 5xx
>>>>> response code for this policy decision?</partha>
>>>>>
>>>>> This presupposes the SRS may make
>>>>>> policy decisions for recording.
>>>>>>
>>>>>> Thanks in advance for your thoughts,
>>>>>> Brad
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On
> Behalf
>>>>>> Of Leon Portman
>>>>>> Sent: Thursday, November 17, 2011 4:47 AM
>>>>>> To: John Elwell
>>>>>> Cc: siprec@ietf.org
>>>>>> Subject: Re: [siprec] Transport of snapshot request
>>>>>>
>>>>>> John, Nice to have you back on the list.
>>>>>>
>>>>>> Actually discussion during IETF meeting was started to converge
> to
>>>>>> similar as you describe below.
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> Leon
>>>>>>
>>>>>> On Nov 17, 2011, at 5:15 PM, John Elwell wrote:
>>>>>>
>>>>>>> There has been a long thread discussing the SIP messages for
> snapshot
>>>>>> requests.
>>>>>>>
>>>>>>> First, I see no reason to tie the snapshot request and the
> metadata
>>>>>> transmission to the same transaction (request/response). If they
> are
>>>>>> tied together, this imposes unnecessary time and architectural
>>>>>> constraints on the SRC.
>>>>>
>>>>> <partha>    The model proposed is request/provisional
> response/response
>>>>> Wherein RE-INVITE/100/200 trying shall be used wherein there is no
>>>>> Immediate response to SRS.</partha>
>>>>>
>>>>> I much prefer an approach similar to the
>>>>>> subscribe/notify approach of RFC 3265 - use different
> transactions.
>>>>>
>>>>> <partha>    The downside of this approach is 4 SIP messages per
> every
>>>>> Service. I'm seeing the middle ground of offerless RE-INVITE with
>>>>> Provisional response (100) and final response wherein 3 messages
> are
>>>>> Involved but there is no extra offer/answer race condition from
> SRS.
>>>>>
>>>>> Having said that, in case it is confirmed that SRS will never
> offer
>>>>> Then I'm fine with UPDATE based snapshot request</partha>
>>>>>
>>>>>    I am
>>>>>> rather unsympathetic to allowing, as an option, metadata
> transmission in
>>>>>> a response. Apart from the timing and architectural concerns,
> there is
>>>>>> no means of responding to a response if anything is wrong. Keep
> it
>>>>>> simple, and allow metadata transmission only in requests, as in
> NOTIFY.
>>>>>>>
>>>>>>> Second, I think it is an SRC decision whether it needs a further
>>>>>> offer-answer exchange. When sending the request containing the
> metadata,
>>>>>> the SRC must ensure that any references to media description
> labels are
>>>>>> consistent with the last SDP sent by the SRC - if not, the SRC
> can
>>>>>> initiate a further offer-answer exchange at the same time as the
>>>>>> metadata transmission.
>>>>>>>
>>>>>>> Perhaps it is my imagination, but I thought we had on the table
> at one
>>>>>> time the notion of:
>>>>>>> - SRS sends snapshot request in an UPDATE request.
>>>>>>> - SRC sends medata in an UPDATE request (with offer if it needs
> to
>>>>>> change SDP, otherwise without).
>>>>>>>
>>>>>>> I have lost track of how we came to diverge from this simple
> model.
>>>>>>>
>>>>>>> John
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> siprec mailing list
>>>>>>> siprec@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>>
>>>>>> _______________________________________________
>>>>>> siprec mailing list
>>>>>> siprec@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>> _______________________________________________
>>>>>> siprec mailing list
>>>>>> siprec@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>> _______________________________________________
>>>>> siprec mailing list
>>>>> siprec@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>>
>>>>
>>>> _______________________________________________
>>>> siprec mailing list
>>>> siprec@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>
>>>
>>
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
>


From john.r.elwell@gmail.com  Fri Dec  2 09:52:05 2011
Return-Path: <john.r.elwell@gmail.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69E371F0C76 for <siprec@ietfa.amsl.com>; Fri,  2 Dec 2011 09:52:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cSpNWVtx2-MG for <siprec@ietfa.amsl.com>; Fri,  2 Dec 2011 09:52:04 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 065891F0C6C for <siprec@ietf.org>; Fri,  2 Dec 2011 09:52:03 -0800 (PST)
Received: by bkbzt19 with SMTP id zt19so4362609bkb.31 for <siprec@ietf.org>; Fri, 02 Dec 2011 09:52:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:from:to:cc:references:subject:date:mime-version :content-type:content-transfer-encoding:x-priority:x-msmail-priority :x-mailer:x-mimeole; bh=PI37sQ3I7Ime73OpLOmhpv7PsbAy+B48gIRTw26LXQ4=; b=SarbtqBqMNJSwrorCrDe0NKwGh1l1KTDIy/c5t+iYcRzukT9OrxjYkwHxiwcvEmHW7 QKLzuhJAh69K/vVJXs+yz2FcRpX/37S/eJaTdnmJ2D1HRa2G9GCXS5XB2/XqME51U+lM lAfMyxYk7EfjkJaB66ixMv8zJYcoWyWvkX6Ko=
Received: by 10.205.120.2 with SMTP id fw2mr11364064bkc.10.1322848323020; Fri, 02 Dec 2011 09:52:03 -0800 (PST)
Received: from JohnsComputer (cpc1-clif8-2-0-cust418.12-4.cable.virginmedia.com. [82.25.209.163]) by mx.google.com with ESMTPS id z7sm18380443bka.1.2011.12.02.09.52.00 (version=SSLv3 cipher=OTHER); Fri, 02 Dec 2011 09:52:00 -0800 (PST)
Message-ID: <A77EBC7712054357A13C183B3703C1A4@JohnsComputer>
From: "John Elwell" <john.r.elwell@gmail.com>
To: "Hadriel Kaplan" <HKaplan@acmepacket.com>, "Paul Kyzivat" <pkyzivat@alum.mit.edu>
References: <B20359D2613947B69891A631964F8457@JohnsComputer><6ACE27C1-E11E-4137-A0E9-81BDF6C0E524@gmail.com><622B0E14298DDE47ACA9E16B292F22A40F2F7EB2@Mail1.acmepacket.com><387F9047F55E8C42850AD6B3A7A03C6C01D9D17E@inba-mail02.sonusnet.com><4ED6EAA3.6060708@alum.mit.edu> <AB722865-2E55-4184-86A5-288B344B650C@acmepacket.com>
Date: Fri, 2 Dec 2011 17:52:15 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Cc: siprec@ietf.org
Subject: Re: [siprec] Transport of snapshot request
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2011 17:52:05 -0000

I am happy with the notion of keeping options to a minimum. However, I 
prefer to decouple the snapshot request and the snapshot into different 
transactions (rather like SUBSCRIBE and NOTIFY). The snapshot itself can 
then be done the same way as any metadata update (except we might choose to 
mandate that a snapshot be accompanied by an SDP offer, even though a 
regular update might be with or without an SDP offer). So a simple approach 
might be:
- UPDATE request (without SDP offer) for snapshot request;
- UPDATE request (with/without SDP offer) for metadata update or snapshot.

John

----- Original Message ----- 
From: "Hadriel Kaplan" <HKaplan@acmepacket.com>
To: "Paul Kyzivat" <pkyzivat@alum.mit.edu>
Cc: <siprec@ietf.org>
Sent: Thursday, December 01, 2011 3:28 PM
Subject: Re: [siprec] Transport of snapshot request


>
> The reason to "exclude" anything is to improve interoperability.  I've 
> seen countless issues with implementations not expecting another device to 
> do something causing problems when the other device does it, and 
> definitely for re-INVITEs and UPDATE scenarios.
>
> So unless there's some pressing need to support multiple possible 
> scenarios, I don't see any reason not to just pick one and only one way to 
> do something - it will improve interop to do so.
>
> If we think a snapshot request from the SRS will usually need SDP from the 
> SRC, and we don't think the SRS can provide an SDP offer in the snapshot 
> request - and I don't think the SRS can in fact always provide an SDP 
> offer in it because the whole reason it's asking for a snapshot is it 
> forgot stuff - then we should pick a way to do it without requiring the 
> SRS to send an SDP offer.
>
> Ergo, I vote we pick the snapshot request mechanism be an offerless 
> re-INVITE, period.  That will work in every scenario anyone has ever 
> mentioned, afaict, and thus there's no reason to do anything else.  No?
>
> -hadriel
>
>
> On Nov 30, 2011, at 9:46 PM, Paul Kyzivat wrote:
>
>> On 12/1/11 8:47 AM, Ravindran, Parthasarathi wrote:
>>> Hi all,
>>>
>>> I agree with UPDATE without SDP based snapshot request in case there is
>>> an agreement that SRS will never generate offer as there is no 
>>> possibility
>>> of offer-answer race condition based on snapshot request mechanism. So,
>>> I'm interested in hearing everybody opinion on "no offer from SRS" 
>>> stance
>>> For SIPREC.
>>
>> I don't see how it would ever make sense for the SRS to make an offer to 
>> the SRC, so I'm fine with declaring that invalid SRS behavior.
>>
>> As far as a snapshot without SDP, I agree it is unlikely that a snapshot 
>> would not require an SDP update. But I see no reason to exclude it in the 
>> unlikely event that a case comes up when it is valid.
>>
>> This would be a problem if a snapshot request was in an UPDATE without 
>> SDP and the snapshot was required to be in the reply. But as long as the 
>> SRC can wait and send the snapshot in a request it initiates, it can make 
>> any offer it needs to, or potentially it could do the snapshot in an 
>> UPDATE without SDP if no SDP was needed.
>>
>> Thanks,
>> Paul
>>
>>> Brad/John,
>>>
>>> Please read inline.
>>>
>>> Thanks
>>> Partha
>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On 
>>>> Behalf
>>>> Of Brad Winslow
>>>> Sent: Wednesday, November 23, 2011 10:23 PM
>>>> To: siprec@ietf.org
>>>> Subject: Re: [siprec] Transport of snapshot request
>>>>
>>>> Hi Folks,
>>>>
>>>> In the situation where the SRS needs a metadata update, it most likely
>>>> will need an SDP update, as there is no guarantee the metadata-only
>>>> update would be consistent with the current SDP label attributes of the
>>>> SRS, aren't we asking for trouble if we allow a metadata-only update?
>>> <partha>  Snapshot request UPDATE without SDP from SRS is used to 
>>> trigger
>>> Metadata request in SRC using RE-INVITE or UPDATE method
>>> </partha>
>>>
>>>> If we decide on a full update, metadata + SDP, should we settle on
>>>> UPDATE or INVITE to transmit the update from SRC to SRS?
>>> <partha>  We have common understanding here</partha>
>>>
>>>>
>>>> As an aside, there is an expectation that the SRC behaves as a SIP UA,
>>>> in this case it should be able to respond to an offer-less re-INVITE
>>>> from the SRS and provide metadata and SDP in the response.
>>>>
>>> <partha>  offerless Re-INVITE with 100 + 200 response is currently 
>>> considered
>>> as alternative Proposal to UPDATE without SDP snapshot request</partha>
>>>
>>>> Finally, if the SRS receives an INVITE for a new recording session,
>>>> should we have an error code response which indicates the SRS is not
>>>> interested in recording the session, not as a failure status, just as a
>>>> status to terminate the recording.
>>>
>>> <partha>  It will be negative response in case INVITE with 
>>> require:siprec is
>>> not accepted using 200 OK right? Do we need the new server negative 5xx
>>> response code for this policy decision?</partha>
>>>
>>> This presupposes the SRS may make
>>>> policy decisions for recording.
>>>>
>>>> Thanks in advance for your thoughts,
>>>> Brad
>>>>
>>>> -----Original Message-----
>>>> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On 
>>>> Behalf
>>>> Of Leon Portman
>>>> Sent: Thursday, November 17, 2011 4:47 AM
>>>> To: John Elwell
>>>> Cc: siprec@ietf.org
>>>> Subject: Re: [siprec] Transport of snapshot request
>>>>
>>>> John, Nice to have you back on the list.
>>>>
>>>> Actually discussion during IETF meeting was started to converge to
>>>> similar as you describe below.
>>>>
>>>> Regards
>>>>
>>>> Leon
>>>>
>>>> On Nov 17, 2011, at 5:15 PM, John Elwell wrote:
>>>>
>>>>> There has been a long thread discussing the SIP messages for snapshot
>>>> requests.
>>>>>
>>>>> First, I see no reason to tie the snapshot request and the metadata
>>>> transmission to the same transaction (request/response). If they are
>>>> tied together, this imposes unnecessary time and architectural
>>>> constraints on the SRC.
>>>
>>> <partha>  The model proposed is request/provisional response/response
>>> Wherein RE-INVITE/100/200 trying shall be used wherein there is no
>>> Immediate response to SRS.</partha>
>>>
>>> I much prefer an approach similar to the
>>>> subscribe/notify approach of RFC 3265 - use different transactions.
>>>
>>> <partha>  The downside of this approach is 4 SIP messages per every
>>> Service. I'm seeing the middle ground of offerless RE-INVITE with
>>> Provisional response (100) and final response wherein 3 messages are
>>> Involved but there is no extra offer/answer race condition from SRS.
>>>
>>> Having said that, in case it is confirmed that SRS will never offer
>>> Then I'm fine with UPDATE based snapshot request</partha>
>>>
>>>  I am
>>>> rather unsympathetic to allowing, as an option, metadata transmission 
>>>> in
>>>> a response. Apart from the timing and architectural concerns, there is
>>>> no means of responding to a response if anything is wrong. Keep it
>>>> simple, and allow metadata transmission only in requests, as in NOTIFY.
>>>>>
>>>>> Second, I think it is an SRC decision whether it needs a further
>>>> offer-answer exchange. When sending the request containing the 
>>>> metadata,
>>>> the SRC must ensure that any references to media description labels are
>>>> consistent with the last SDP sent by the SRC - if not, the SRC can
>>>> initiate a further offer-answer exchange at the same time as the
>>>> metadata transmission.
>>>>>
>>>>> Perhaps it is my imagination, but I thought we had on the table at one
>>>> time the notion of:
>>>>> - SRS sends snapshot request in an UPDATE request.
>>>>> - SRC sends medata in an UPDATE request (with offer if it needs to
>>>> change SDP, otherwise without).
>>>>>
>>>>> I have lost track of how we came to diverge from this simple model.
>>>>>
>>>>> John
>>>>>
>>>>> _______________________________________________
>>>>> siprec mailing list
>>>>> siprec@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>>
>>>> _______________________________________________
>>>> siprec mailing list
>>>> siprec@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/siprec
>>>> _______________________________________________
>>>> siprec mailing list
>>>> siprec@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/siprec
>>> _______________________________________________
>>> siprec mailing list
>>> siprec@ietf.org
>>> https://www.ietf.org/mailman/listinfo/siprec
>>>
>>
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
>
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec 


From andrew.hutton@siemens-enterprise.com  Fri Dec  9 03:57:42 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBA8D21F86A1 for <siprec@ietfa.amsl.com>; Fri,  9 Dec 2011 03:57:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.669
X-Spam-Level: 
X-Spam-Status: No, score=-1.669 tagged_above=-999 required=5 tests=[AWL=-0.930, BAYES_20=-0.74, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1sr38Pc83aY0 for <siprec@ietfa.amsl.com>; Fri,  9 Dec 2011 03:57:42 -0800 (PST)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 529F421F86AA for <siprec@ietf.org>; Fri,  9 Dec 2011 03:57:42 -0800 (PST)
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id BC27E1EB84FE for <siprec@ietf.org>; Fri,  9 Dec 2011 12:57:38 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Fri, 9 Dec 2011 12:57:38 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Fri, 9 Dec 2011 12:57:37 +0100
Thread-Topic: IETF 82 Minutes.
Thread-Index: Acy2ab5eyh2mUMVjThmFb6AUeSd4oA==
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311FAE70EB6@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_101C6067BEC68246B0C3F6843BCCC1E311FAE70EB6MCHP058Agloba_"
MIME-Version: 1.0
Subject: [siprec] IETF 82 Minutes.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Dec 2011 11:57:43 -0000

--_000_101C6067BEC68246B0C3F6843BCCC1E311FAE70EB6MCHP058Agloba_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

SIPREC IETF82 minutes can be found at http://www.ietf.org/proceedings/82/mi=
nutes/siprec.txt.

Any issues with these then please let me know and I will check against the =
audio and correct if necessary.

Lets kick start some discussion on the open issues since we have all had a =
few weeks now to recover after Taipei.

Regards
Andy


--_000_101C6067BEC68246B0C3F6843BCCC1E311FAE70EB6MCHP058Agloba_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri, sans-serif" size=3D"2">
<div>SIPREC IETF82 minutes can be found at <a href=3D"http://www.ietf.org/p=
roceedings/82/minutes/siprec.txt"><font color=3D"#0000FF"><u>http://www.iet=
f.org/proceedings/82/minutes/siprec.txt</u></font></a><b>.</b></div>
<div>&nbsp;</div>
<div>Any issues with these then please let me know and I will check against=
 the audio and correct if necessary.</div>
<div>&nbsp;</div>
<div>Lets kick start some discussion on the open issues since we have all h=
ad a few weeks now to recover after Taipei.</div>
<div>&nbsp;</div>
<div>Regards</div>
<div>Andy</div>
<div>&nbsp;</div>
</font>
</body>
</html>

--_000_101C6067BEC68246B0C3F6843BCCC1E311FAE70EB6MCHP058Agloba_--

From andrew.hutton@siemens-enterprise.com  Fri Dec  9 08:34:00 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D3A721F84B2 for <siprec@ietfa.amsl.com>; Fri,  9 Dec 2011 08:34:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.133
X-Spam-Level: 
X-Spam-Status: No, score=-2.133 tagged_above=-999 required=5 tests=[AWL=0.464,  BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02g0oC1hCM+8 for <siprec@ietfa.amsl.com>; Fri,  9 Dec 2011 08:34:00 -0800 (PST)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id CF5C621F845E for <siprec@ietf.org>; Fri,  9 Dec 2011 08:33:59 -0800 (PST)
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id 110241EB848C for <siprec@ietf.org>; Fri,  9 Dec 2011 17:33:59 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Fri, 9 Dec 2011 17:33:58 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Importance: high
X-Priority: 1
Date: Fri, 9 Dec 2011 17:34:05 +0100
Thread-Topic: SIPREC Interim - Would you attend in San Jose.
Thread-Index: Acy2kF4m4Fu11k7CS7uNQ8B5GkBYBA==
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311FAE710C2@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_101C6067BEC68246B0C3F6843BCCC1E311FAE710C2MCHP058Agloba_"
MIME-Version: 1.0
Subject: [siprec] SIPREC Interim - Would you attend in San Jose.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Dec 2011 16:34:00 -0000

--_000_101C6067BEC68246B0C3F6843BCCC1E311FAE710C2MCHP058Agloba_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

It looks like RTCWEB will be having a face to face interim in San Jose on t=
he 31st Jan and 1st of Feb 2012 there will I believe be at least some peopl=
e attending this who are active in SIPREC.

If we could arrange a SIPREC interim at the same location on the 2nd of Feb=
ruary would you attend in person?

Please let me know by the 16th of December if there is at least a high prob=
ability of you attending such a SIPREC interim.

Regards
Andy




--_000_101C6067BEC68246B0C3F6843BCCC1E311FAE710C2MCHP058Agloba_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri, sans-serif" size=3D"2">
<div>Hi All,</div>
<div>&nbsp;</div>
<div>It looks like RTCWEB will be having a face to face interim in San Jose=
 on the 31<font size=3D"1"><sup>st</sup></font> Jan and 1<font size=3D"1"><=
sup>st</sup></font> of Feb 2012 there will I believe be at least some peopl=
e attending this who are active in SIPREC.</div>
<div>&nbsp;</div>
<div>If we could arrange a SIPREC interim at the same location on the 2<fon=
t size=3D"1"><sup>nd</sup></font> of February would you attend in person?</=
div>
<div>&nbsp;</div>
<div>Please let me know by the 16<font size=3D"1"><sup>th</sup></font> of D=
ecember if there is at least a high probability of you attending such a SIP=
REC interim.</div>
<div>&nbsp;</div>
<div>Regards</div>
<div>Andy</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
</font>
</body>
</html>

--_000_101C6067BEC68246B0C3F6843BCCC1E311FAE710C2MCHP058Agloba_--

From leon.portman@gmail.com  Fri Dec  9 08:53:44 2011
Return-Path: <leon.portman@gmail.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1442921F84A8 for <siprec@ietfa.amsl.com>; Fri,  9 Dec 2011 08:53:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uI4U2BJ1oesX for <siprec@ietfa.amsl.com>; Fri,  9 Dec 2011 08:53:43 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 71E4621F84F9 for <siprec@ietf.org>; Fri,  9 Dec 2011 08:53:41 -0800 (PST)
Received: by vbbez10 with SMTP id ez10so2649554vbb.31 for <siprec@ietf.org>; Fri, 09 Dec 2011 08:53:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=W4ELiXuw02Bgq2qhuCix+GaJ7wkfJ5k8aYI0G9MlKy8=; b=jUgbIc1MT18/YEVVGEaCDeSQcIdDeplUKSLjXTaGUsZNK9Bhpe37Vy2tSvr4G0PGr+ SbB/EJ8BF1ELxMSB84qGzCq3nOtjNhdGj9tiOPATqbHdL+umd2pucUFuROMIHFFzzk0X gQsVBdnOcUwvYc8JbYi1dZQbk2C9z01PnxN2Y=
MIME-Version: 1.0
Received: by 10.52.240.206 with SMTP id wc14mr4841614vdc.126.1323449620699; Fri, 09 Dec 2011 08:53:40 -0800 (PST)
Received: by 10.220.177.74 with HTTP; Fri, 9 Dec 2011 08:53:40 -0800 (PST)
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311FAE710C2@MCHP058A.global-ad.net>
References: <101C6067BEC68246B0C3F6843BCCC1E311FAE710C2@MCHP058A.global-ad.net>
Date: Fri, 9 Dec 2011 18:53:40 +0200
Message-ID: <CAL0XzEJk9CStdtJ_dt1k8u1vPYvBK6HSsJnOa5+Th2p+ucZt0g@mail.gmail.com>
From: Leon Portman <leon.portman@gmail.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>,  "siprec@ietf.org" <siprec@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [siprec] SIPREC Interim - Would you attend in San Jose.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Dec 2011 16:53:44 -0000

Yes, myself and additional developer from NICE can attend.

Regards

Leon

On 12/9/11, Hutton, Andrew <andrew.hutton@siemens-enterprise.com> wrote:
> Hi All,
>
> It looks like RTCWEB will be having a face to face interim in San Jose on
> the 31st Jan and 1st of Feb 2012 there will I believe be at least some
> people attending this who are active in SIPREC.
>
> If we could arrange a SIPREC interim at the same location on the 2nd of
> February would you attend in person?
>
> Please let me know by the 16th of December if there is at least a high
> probability of you attending such a SIPREC interim.
>
> Regards
> Andy
>
>
>
>

-- 
Sent from my mobile device

From krehor@cisco.com  Fri Dec  9 08:55:36 2011
Return-Path: <krehor@cisco.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BD1221F8753 for <siprec@ietfa.amsl.com>; Fri,  9 Dec 2011 08:55:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.202
X-Spam-Level: 
X-Spam-Status: No, score=-5.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LfG1MIx9hqMT for <siprec@ietfa.amsl.com>; Fri,  9 Dec 2011 08:55:35 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 1BC8D21F8531 for <siprec@ietf.org>; Fri,  9 Dec 2011 08:55:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=krehor@cisco.com; l=3405; q=dns/txt; s=iport; t=1323449735; x=1324659335; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version; bh=mpgl6HlJIlgk9OTa1Fq1SDITmGJEvjMH25S2MXbyhos=; b=HGYxKoRnxbo+yYyL7GUDezaRwtrPFy2bPjFI2CcsY7LlUVvDiZUbkzpK KqMTpjMyue83vjvDhCzWmfUEBNu8+Ur+Qv52wLpmzf3NzZhdLFK7rKU4G If4hsGl2tgDKm+Crcsrt4xBMzaGfSsDRG6vnwu7j+c5M3OJMUJoHPbgIL o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAP084k6rRDoJ/2dsb2JhbABDgk2nHYEPgQWBcgEBAQECAQEBAQ8BKjELBQ0BCARpMAEBBA4FIodlCJdXAZ4EBItyBId9M4xAkkg
X-IronPort-AV: E=Sophos;i="4.71,326,1320624000"; d="scan'208,217";a="18951854"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 09 Dec 2011 16:55:35 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pB9GtYTn024636; Fri, 9 Dec 2011 16:55:34 GMT
Received: from xmb-sjc-22e.amer.cisco.com ([128.107.191.115]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 9 Dec 2011 08:55:34 -0800
Received: from 10.20.172.21 ([10.20.172.21]) by xmb-sjc-22e.amer.cisco.com ([128.107.191.115]) with Microsoft Exchange Server HTTP-DAV ;  Fri,  9 Dec 2011 16:55:34 +0000
User-Agent: Microsoft-Entourage/12.31.0.110725
Date: Fri, 09 Dec 2011 08:55:27 -0800
From: Ken Rehor <krehor@cisco.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
Message-ID: <CB077D7F.24BA6%krehor@cisco.com>
Thread-Topic: [siprec] SIPREC Interim - Would you attend in San Jose.
Thread-Index: Acy2kF4m4Fu11k7CS7uNQ8B5GkBYBAAAvumJ
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311FAE710C2@MCHP058A.global-ad.net>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3406265729_49792898"
X-OriginalArrivalTime: 09 Dec 2011 16:55:34.0525 (UTC) FILETIME=[5E49E2D0:01CCB693]
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] SIPREC Interim - Would you attend in San Jose.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Dec 2011 16:55:36 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3406265729_49792898
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Hi Andy,

That would be very convenient for me since I haven=B9t been able to travel to
the other meetings lately.

Ken


On 12/9/11 8:34 AM, "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
wrote:

> Hi All,
> =20
> It looks like RTCWEB will be having a face to face interim in San Jose on=
 the
> 31st Jan and 1st of Feb 2012 there will I believe be at least some people
> attending this who are active in SIPREC.
> =20
> If we could arrange a SIPREC interim at the same location on the 2nd of
> February would you attend in person?
> =20
> Please let me know by the 16th of December if there is at least a high
> probability of you attending such a SIPREC interim.
> =20
> Regards
> Andy
> =20
> =20
> =20
>=20
>=20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec


--B_3406265729_49792898
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [siprec] SIPREC Interim - Would you attend in San Jose.</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'>Hi Andy,<BR>
<BR>
That would be very convenient for me since I haven&#8217;t been able to tra=
vel to the other meetings lately. <BR>
<BR>
Ken<BR>
<BR>
<BR>
On 12/9/11 8:34 AM, &quot;Hutton, Andrew&quot; &lt;<a href=3D"andrew.hutton@s=
iemens-enterprise.com">andrew.hutton@siemens-enterprise.com</a>&gt; wrote:<B=
R>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><=
SPAN STYLE=3D'font-size:11pt'>Hi All,<BR>
&nbsp;<BR>
It looks like RTCWEB will be having a face to face interim in San Jose on t=
he 31</SPAN><FONT SIZE=3D"2"><SPAN STYLE=3D'font-size:10pt'>st</SPAN></FONT><SPA=
N STYLE=3D'font-size:11pt'> Jan and 1</SPAN><FONT SIZE=3D"2"><SPAN STYLE=3D'font-s=
ize:10pt'>st</SPAN></FONT><SPAN STYLE=3D'font-size:11pt'> of Feb 2012 there wi=
ll I believe be at least some people attending this who are active in SIPREC=
.<BR>
&nbsp;<BR>
If we could arrange a SIPREC interim at the same location on the 2</SPAN><F=
ONT SIZE=3D"2"><SPAN STYLE=3D'font-size:10pt'>nd</SPAN></FONT><SPAN STYLE=3D'font-=
size:11pt'> of February would you attend in person?<BR>
&nbsp;<BR>
Please let me know by the 16</SPAN><FONT SIZE=3D"2"><SPAN STYLE=3D'font-size:10=
pt'>th</SPAN></FONT><SPAN STYLE=3D'font-size:11pt'> of December if there is at=
 least a high probability of you attending such a SIPREC interim.<BR>
&nbsp;<BR>
Regards<BR>
Andy<BR>
&nbsp;<BR>
&nbsp;<BR>
&nbsp;<BR>
<BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"></SPAN></FONT><FONT SIZE=3D"2"><FONT FA=
CE=3D"Consolas, Courier New, Courier"><SPAN STYLE=3D'font-size:10pt'>___________=
____________________________________<BR>
siprec mailing list<BR>
<a href=3D"siprec@ietf.org">siprec@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/siprec">https://www.ietf.org=
/mailman/listinfo/siprec</a><BR>
</SPAN></FONT></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3406265729_49792898--


From andrew.hutton@siemens-enterprise.com  Fri Dec 16 11:57:20 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23C2C11E8089 for <siprec@ietfa.amsl.com>; Fri, 16 Dec 2011 11:57:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.359
X-Spam-Level: 
X-Spam-Status: No, score=-1.359 tagged_above=-999 required=5 tests=[AWL=-0.620, BAYES_20=-0.74, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kXbPLyS9X-5S for <siprec@ietfa.amsl.com>; Fri, 16 Dec 2011 11:57:19 -0800 (PST)
Received: from senmx12-mx.siemens-enterprise.com (senmx12-mx.siemens-enterprise.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 85FDF11E809D for <siprec@ietf.org>; Fri, 16 Dec 2011 11:57:18 -0800 (PST)
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id E5F3623F050B for <siprec@ietf.org>; Fri, 16 Dec 2011 20:57:14 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Fri, 16 Dec 2011 20:57:14 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Fri, 16 Dec 2011 20:57:13 +0100
Thread-Topic: SIPREC Interim - Would you attend in San Jose.
Thread-Index: Acy2kF4m4Fu11k7CS7uNQ8B5GkBYBAFeu3pg
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311FD73943D@MCHP058A.global-ad.net>
References: <101C6067BEC68246B0C3F6843BCCC1E311FAE710C2@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311FAE710C2@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_101C6067BEC68246B0C3F6843BCCC1E311FD73943DMCHP058Agloba_"
MIME-Version: 1.0
Subject: Re: [siprec] SIPREC Interim - Would you attend in San Jose.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 19:57:20 -0000

--_000_101C6067BEC68246B0C3F6843BCCC1E311FD73943DMCHP058Agloba_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

I have only had a very limited response to this request and therefore I don=
't think we can justify having a f2f interim co-located with the RTCWEB mee=
ting.

However there is an alternative and that would be co-locating with the CLUE=
 meeting and having the meeting in the Boston area on the 17th of February.=
 This would give us until the middle of January to make a final decision an=
d to make some progress via the mailing list. Lets kick start some more dis=
cussion on the list there are a number of IETF82 actions that need further =
discussion.

I will also create a doodle poll to see who would commit to an interim meet=
ing in Boston.

Regards
Andy





From: siprec-bounces@ietf.org<mailto:siprec-bounces@ietf.org> [mailto:sipre=
c-bounces@ietf.org] On Behalf Of Hutton, Andrew
Sent: 09 December 2011 16:34
To: siprec@ietf.org<mailto:siprec@ietf.org>
Subject: [siprec] SIPREC Interim - Would you attend in San Jose.
Importance: High

Hi All,

It looks like RTCWEB will be having a face to face interim in San Jose on t=
he 31st Jan and 1st of Feb 2012 there will I believe be at least some peopl=
e attending this who are active in SIPREC.

If we could arrange a SIPREC interim at the same location on the 2nd of Feb=
ruary would you attend in person?

Please let me know by the 16th of December if there is at least a high prob=
ability of you attending such a SIPREC interim.

Regards
Andy




--_000_101C6067BEC68246B0C3F6843BCCC1E311FD73943DMCHP058Agloba_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi All,<o=
:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif";color:#1F497D'>I have only had a very limited response to thi=
s request and therefore I don&#8217;t think we can justify having a f2f int=
erim co-located with the RTCWEB meeting.<o:p></o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";=
color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Howe=
ver there is an alternative and that would be co-locating with the CLUE mee=
ting and having the meeting in the Boston area on the 17<sup>th</sup> of Fe=
bruary. This would give us until the middle of January to make a final deci=
sion and to make some progress via the mailing list. Lets kick start some m=
ore discussion on the list there are a number of IETF82 actions that need f=
urther discussion.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&n=
bsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif";color:#1F497D'>I will also create a doodl=
e poll to see who would commit to an interim meeting in Boston.<o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:=
"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'>Regards<o:p></o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'>Andy<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></=
span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"=
Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:=
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p><=
/span></p><div style=3D'border:none;border-left:solid blue 1.5pt;padding:0c=
m 0cm 0cm 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF 1.=
0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US s=
tyle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b=
><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma","sans-se=
rif"'> <a href=3D"mailto:siprec-bounces@ietf.org">siprec-bounces@ietf.org</=
a> [<a href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-bounces@ietf.o=
rg</a>] <b>On Behalf Of </b>Hutton, Andrew<br><b>Sent:</b> 09 December 2011=
 16:34<br><b>To:</b> <a href=3D"mailto:siprec@ietf.org">siprec@ietf.org</a>=
<br><b>Subject:</b> [siprec] SIPREC Interim - Would you attend in San Jose.=
<br><b>Importance:</b> High<o:p></o:p></span></p></div></div><p class=3DMso=
Normal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span style=3D'font-s=
ize:10.0pt;font-family:"Calibri","sans-serif"'>Hi All,<o:p></o:p></span></p=
></div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-famil=
y:"Calibri","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><div><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Calibri","sans-se=
rif"'>It looks like RTCWEB will be having a face to face interim in San Jos=
e on the 31</span><sup><span style=3D'font-size:7.5pt;font-family:"Calibri"=
,"sans-serif"'>st</span></sup><span style=3D'font-size:10.0pt;font-family:"=
Calibri","sans-serif"'> Jan and 1</span><sup><span style=3D'font-size:7.5pt=
;font-family:"Calibri","sans-serif"'>st</span></sup><span style=3D'font-siz=
e:10.0pt;font-family:"Calibri","sans-serif"'> of Feb 2012 there will I beli=
eve be at least some people attending this who are active in SIPREC.<o:p></=
o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.=
0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><=
div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Calib=
ri","sans-serif"'>If we could arrange a SIPREC interim at the same location=
 on the 2</span><sup><span style=3D'font-size:7.5pt;font-family:"Calibri","=
sans-serif"'>nd</span></sup><span style=3D'font-size:10.0pt;font-family:"Ca=
libri","sans-serif"'> of February would you attend in person?<o:p></o:p></s=
pan></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fon=
t-family:"Calibri","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Calibri","sa=
ns-serif"'>Please let me know by the 16</span><sup><span style=3D'font-size=
:7.5pt;font-family:"Calibri","sans-serif"'>th</span></sup><span style=3D'fo=
nt-size:10.0pt;font-family:"Calibri","sans-serif"'> of December if there is=
 at least a high probability of you attending such a SIPREC interim.<o:p></=
o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.=
0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><=
div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Calib=
ri","sans-serif"'>Regards<o:p></o:p></span></p></div><div><p class=3DMsoNor=
mal><span style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>And=
y<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-=
size:10.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p></o:p></span></p=
></div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-famil=
y:"Calibri","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><div><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Calibri","sans-se=
rif"'>&nbsp;<o:p></o:p></span></p></div></div></div></body></html>=

--_000_101C6067BEC68246B0C3F6843BCCC1E311FD73943DMCHP058Agloba_--

From leon.portman@gmail.com  Fri Dec 16 12:03:52 2011
Return-Path: <leon.portman@gmail.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60DF421F8783 for <siprec@ietfa.amsl.com>; Fri, 16 Dec 2011 12:03:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5HdQ0Hn9UuMm for <siprec@ietfa.amsl.com>; Fri, 16 Dec 2011 12:03:51 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 52B9621F877F for <siprec@ietf.org>; Fri, 16 Dec 2011 12:03:51 -0800 (PST)
Received: by werb14 with SMTP id b14so669569wer.31 for <siprec@ietf.org>; Fri, 16 Dec 2011 12:03:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=7QPznKmtTvX3nJ3jgvWtbmEswVxhj5cq7fefL2qoAtg=; b=mK8y9aenF5i3ckhJNEh1HQhf+xEQhckpYK1d12ctMMHIw+XA0UUZFjzHM5mqNBiUBp Irg0WBMr6o7Z2IKRkuxQqHU6M4oPweCQ61Tyrt1LoXbISIPjErCB1cBirgkz83D3XRlP /uUgJTkJj9L43c+DNdaM5HmbQoYDWNI5AZOeY=
Received: by 10.216.131.141 with SMTP id m13mr1182471wei.30.1324065830542; Fri, 16 Dec 2011 12:03:50 -0800 (PST)
Received: from [192.168.1.105] ([212.150.140.190]) by mx.google.com with ESMTPS id dd4sm14459931wib.1.2011.12.16.12.03.48 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 16 Dec 2011 12:03:49 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1254)
Content-Type: multipart/alternative; boundary="Apple-Mail=_4466C635-FA65-48F6-B7AF-986E134A6CB6"
From: Leon Portman <leon.portman@gmail.com>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311FD73943D@MCHP058A.global-ad.net>
Date: Fri, 16 Dec 2011 22:03:45 +0200
Message-Id: <78828F59-7E32-4CD5-8B2B-76437821B2DF@gmail.com>
References: <101C6067BEC68246B0C3F6843BCCC1E311FAE710C2@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E311FD73943D@MCHP058A.global-ad.net>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
X-Mailer: Apple Mail (2.1254)
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] SIPREC Interim - Would you attend in San Jose.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 20:03:52 -0000

--Apple-Mail=_4466C635-FA65-48F6-B7AF-986E134A6CB6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Andy Hi

Boston will be much colder comparing to San Jose in winter. Will attend =
anyway

Regards

Leon

On Dec 16, 2011, at 9:57 PM, Hutton, Andrew wrote:

> Hi All,
> =20
> I have only had a very limited response to this request and therefore =
I don=92t think we can justify having a f2f interim co-located with the =
RTCWEB meeting.
> =20
> However there is an alternative and that would be co-locating with the =
CLUE meeting and having the meeting in the Boston area on the 17th of =
February. This would give us until the middle of January to make a final =
decision and to make some progress via the mailing list. Lets kick start =
some more discussion on the list there are a number of IETF82 actions =
that need further discussion.
> =20
> I will also create a doodle poll to see who would commit to an interim =
meeting in Boston.
> =20
> Regards
> Andy
> =20
> =20
> =20
> =20
> =20
> From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On =
Behalf Of Hutton, Andrew
> Sent: 09 December 2011 16:34
> To: siprec@ietf.org
> Subject: [siprec] SIPREC Interim - Would you attend in San Jose.
> Importance: High
> =20
> Hi All,
> =20
> It looks like RTCWEB will be having a face to face interim in San Jose =
on the 31st Jan and 1st of Feb 2012 there will I believe be at least =
some people attending this who are active in SIPREC.
> =20
> If we could arrange a SIPREC interim at the same location on the 2nd =
of February would you attend in person?
> =20
> Please let me know by the 16th of December if there is at least a high =
probability of you attending such a SIPREC interim.
> =20
> Regards
> Andy
> =20
> =20
> =20
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec


--Apple-Mail=_4466C635-FA65-48F6-B7AF-986E134A6CB6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><base href=3D"x-msg://56/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div>Andy Hi</div><div><br></div><div>Boston will =
be much colder comparing to San Jose in winter. Will attend =
anyway</div><div><br></div><div>Regards</div><div><br></div><div>Leon</div=
><br><div><div>On Dec 16, 2011, at 9:57 PM, Hutton, Andrew =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-GB" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Hi =
All,<o:p></o:p></span></div><div style=3D"margin-top: 0cm; margin-right: =
0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">I =
have only had a very limited response to this request and therefore I =
don=92t think we can justify having a f2f interim co-located with the =
RTCWEB meeting.<o:p></o:p></span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">However there is an alternative and that would be co-locating with the =
CLUE meeting and having the meeting in the Boston area on the =
17<sup>th</sup><span class=3D"Apple-converted-space">&nbsp;</span>of =
February. This would give us until the middle of January to make a final =
decision and to make some progress via the mailing list. Lets kick start =
some more discussion on the list there are a number of IETF82 actions =
that need further discussion.<o:p></o:p></span></div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">I =
will also create a doodle poll to see who would commit to an interim =
meeting in Boston.<o:p></o:p></span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">Regards<o:p></o:p></span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">Andy<o:p></o:p></span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"border-top-style: none; =
border-right-style: none; border-bottom-style: none; border-width: =
initial; border-color: initial; border-left-style: solid; =
border-left-color: blue; border-left-width: 1.5pt; padding-top: 0cm; =
padding-right: 0cm; padding-bottom: 0cm; padding-left: 4pt; "><div><div =
style=3D"border-right-style: none; border-bottom-style: none; =
border-left-style: none; border-width: initial; border-color: initial; =
border-top-style: solid; border-top-color: rgb(181, 196, 223); =
border-top-width: 1pt; padding-top: 3pt; padding-right: 0cm; =
padding-bottom: 0cm; padding-left: 0cm; "><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><b><span lang=3D"EN-US" =
style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; =
">From:</span></b><span lang=3D"EN-US" style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:siprec-bounces@ietf.org" style=3D"color: blue; =
text-decoration: underline; ">siprec-bounces@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>[<a =
href=3D"mailto:siprec-bounces@ietf.org" style=3D"color: blue; =
text-decoration: underline; ">mailto:siprec-bounces@ietf.org</a>]<span =
class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Hutton, =
Andrew<br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>09 December 2011 =
16:34<br><b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:siprec@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">siprec@ietf.org</a><br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>[siprec] SIPREC Interim - =
Would you attend in San Jose.<br><b>Importance:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>High<o:p></o:p></span></div><=
/div></div><div style=3D"margin-top: 0cm; margin-right: 0cm; =
margin-left: 0cm; margin-bottom: 0.0001pt; font-size: 12pt; font-family: =
'Times New Roman', serif; "><o:p>&nbsp;</o:p></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; ">Hi All,<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; ">&nbsp;<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; ">It looks like RTCWEB will be having a face to face interim =
in San Jose on the 31</span><sup><span style=3D"font-size: 7.5pt; =
font-family: Calibri, sans-serif; ">st</span></sup><span =
style=3D"font-size: 10pt; font-family: Calibri, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span>Jan and 1</span><sup><span =
style=3D"font-size: 7.5pt; font-family: Calibri, sans-serif; =
">st</span></sup><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; "><span class=3D"Apple-converted-space">&nbsp;</span>of Feb =
2012 there will I believe be at least some people attending this who are =
active in SIPREC.<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; ">&nbsp;<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; ">If we could arrange a SIPREC interim at the same location =
on the 2</span><sup><span style=3D"font-size: 7.5pt; font-family: =
Calibri, sans-serif; ">nd</span></sup><span style=3D"font-size: 10pt; =
font-family: Calibri, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span>of February would you =
attend in person?<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; ">&nbsp;<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; ">Please let me know by the 16</span><sup><span =
style=3D"font-size: 7.5pt; font-family: Calibri, sans-serif; =
">th</span></sup><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; "><span class=3D"Apple-converted-space">&nbsp;</span>of =
December if there is at least a high probability of you attending such a =
SIPREC interim.<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; ">&nbsp;<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; ">Regards<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; ">Andy<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; ">&nbsp;<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; ">&nbsp;<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10pt; font-family: Calibri, =
sans-serif; =
">&nbsp;<o:p></o:p></span></div></div></div></div>________________________=
_______________________<br>siprec mailing list<br><a =
href=3D"mailto:siprec@ietf.org">siprec@ietf.org</a><br>https://www.ietf.or=
g/mailman/listinfo/siprec</div></span></blockquote></div><br></body></html=
>=

--Apple-Mail=_4466C635-FA65-48F6-B7AF-986E134A6CB6--

From pkyzivat@alum.mit.edu  Fri Dec 16 15:40:22 2011
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FEFC21F85A8 for <siprec@ietfa.amsl.com>; Fri, 16 Dec 2011 15:40:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.526
X-Spam-Level: 
X-Spam-Status: No, score=-2.526 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D-QfLYFpR+UO for <siprec@ietfa.amsl.com>; Fri, 16 Dec 2011 15:40:21 -0800 (PST)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by ietfa.amsl.com (Postfix) with ESMTP id B4A5D21F85A7 for <siprec@ietf.org>; Fri, 16 Dec 2011 15:40:21 -0800 (PST)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta13.westchester.pa.mail.comcast.net with comcast id 9zaG1i00527AodY5DzgNmf; Fri, 16 Dec 2011 23:40:22 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.229.5]) by omta19.westchester.pa.mail.comcast.net with comcast id 9zgN1i00507duvL3fzgNea; Fri, 16 Dec 2011 23:40:22 +0000
Message-ID: <4EEBD6E4.8050200@alum.mit.edu>
Date: Fri, 16 Dec 2011 18:40:20 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: siprec@ietf.org
References: <101C6067BEC68246B0C3F6843BCCC1E311FAE710C2@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E311FD73943D@MCHP058A.global-ad.net> <78828F59-7E32-4CD5-8B2B-76437821B2DF@gmail.com>
In-Reply-To: <78828F59-7E32-4CD5-8B2B-76437821B2DF@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [siprec] SIPREC Interim - Would you attend in San Jose.
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 23:40:22 -0000

On 12/16/11 3:03 PM, Leon Portman wrote:
> Andy Hi
>
> Boston will be much colder comparing to San Jose in winter. Will attend
> anyway

Wimp! :-)

In any case, so far the weather has been unseasonably warm. It has 
rarely been below freezing yet. We've had highs in the 50s or more 
(Fahrenheit) this week.

We may not have winter this year.
Global warming. :-(

	Paul

From andrew.hutton@siemens-enterprise.com  Sun Dec 18 12:07:39 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20D0021F87D6 for <siprec@ietfa.amsl.com>; Sun, 18 Dec 2011 12:07:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QYzZM5kKetMg for <siprec@ietfa.amsl.com>; Sun, 18 Dec 2011 12:07:37 -0800 (PST)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 59FA221F86A0 for <siprec@ietf.org>; Sun, 18 Dec 2011 12:07:36 -0800 (PST)
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id D88111EB8412 for <siprec@ietf.org>; Sun, 18 Dec 2011 21:07:28 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Sun, 18 Dec 2011 21:07:28 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Sun, 18 Dec 2011 21:07:42 +0100
Thread-Topic: SIPREC Interim - Boston Area, Feb 17th 2012
Thread-Index: Acy2kF4m4Fu11k7CS7uNQ8B5GkBYBAFeu3pgAGyVRzA=
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311FD739527@MCHP058A.global-ad.net>
References: <101C6067BEC68246B0C3F6843BCCC1E311FAE710C2@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E311FD73943D@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311FD73943D@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_101C6067BEC68246B0C3F6843BCCC1E311FD739527MCHP058Agloba_"
MIME-Version: 1.0
Subject: Re: [siprec] SIPREC Interim - Boston Area, Feb 17th 2012
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Dec 2011 20:07:39 -0000

--_000_101C6067BEC68246B0C3F6843BCCC1E311FD739527MCHP058Agloba_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

I created a doodle poll to register an indication of whether or not you wou=
ld attend a face to face SIPREC Interim meeting if it was held in the Bosto=
n (US) area on the 17th of February (i.e. day after the CLUE meeting).  The=
 venue for such a meeting would most likely be the same as for the CLUE mee=
ting (i.e. Polycom office in Andover, MA) unless we get a large number of p=
eople.

Remote participation would be possible but this poll is for the purpose of =
understanding who would actually attend in person.



http://www.doodle.com/q3555taia7xbpmt2



This poll will close on the 6th of January after which the chairs will make=
 a decision as to whether the meeting should take place.

Regards
Andy


From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Hutton, Andrew
Sent: 16 December 2011 19:57
To: siprec@ietf.org
Subject: Re: [siprec] SIPREC Interim - Would you attend in San Jose.

Hi All,

I have only had a very limited response to this request and therefore I don=
't think we can justify having a f2f interim co-located with the RTCWEB mee=
ting.

However there is an alternative and that would be co-locating with the CLUE=
 meeting and having the meeting in the Boston area on the 17th of February.=
 This would give us until the middle of January to make a final decision an=
d to make some progress via the mailing list. Lets kick start some more dis=
cussion on the list there are a number of IETF82 actions that need further =
discussion.

I will also create a doodle poll to see who would commit to an interim meet=
ing in Boston.

Regards
Andy





From: siprec-bounces@ietf.org<mailto:siprec-bounces@ietf.org> [mailto:sipre=
c-bounces@ietf.org] On Behalf Of Hutton, Andrew
Sent: 09 December 2011 16:34
To: siprec@ietf.org<mailto:siprec@ietf.org>
Subject: [siprec] SIPREC Interim - Would you attend in San Jose.
Importance: High

Hi All,

It looks like RTCWEB will be having a face to face interim in San Jose on t=
he 31st Jan and 1st of Feb 2012 there will I believe be at least some peopl=
e attending this who are active in SIPREC.

If we could arrange a SIPREC interim at the same location on the 2nd of Feb=
ruary would you attend in person?

Please let me know by the 16th of December if there is at least a high prob=
ability of you attending such a SIPREC interim.

Regards
Andy




--_000_101C6067BEC68246B0C3F6843BCCC1E311FD739527MCHP058Agloba_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi All,<o=
:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif";color:#1F497D'>I created a doodle poll to register an indicat=
ion of whether or not you would attend a face to face SIPREC Interim meetin=
g if it was held in the Boston (US) area on the 17<sup>th</sup> of February=
 (i.e. day after the CLUE meeting).&nbsp; The venue for such a meeting woul=
d most likely be the same as for the CLUE meeting (i.e. Polycom office in A=
ndover, MA) unless we get a large number of people.<o:p></o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'>Remote participation would be possible but this poll is for the purp=
ose of understanding who would actually attend in person.<o:p></o:p></span>=
</p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>=
<p class=3DMsoPlainText><span lang=3DEN-US><a href=3D"http://www.doodle.com=
/q3555taia7xbpmt2">http://www.doodle.com/q3555taia7xbpmt2</a><o:p></o:p></s=
pan></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoPlainText><span lang=3DEN-US>This poll will close on the =
6<sup>th</sup> of January after which the chairs will make a decision as to=
 whether the meeting should take place.<o:p></o:p></span></p><p class=3DMso=
Normal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";c=
olor:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Rega=
rds<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'>Andy<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calib=
ri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoN=
ormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";co=
lor:#1F497D'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-l=
eft:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:n=
one;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMs=
oNormal><b><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span lang=3DEN-US style=3D'font-size:10.0p=
t;font-family:"Tahoma","sans-serif"'> siprec-bounces@ietf.org [mailto:sipre=
c-bounces@ietf.org] <b>On Behalf Of </b>Hutton, Andrew<br><b>Sent:</b> 16 D=
ecember 2011 19:57<br><b>To:</b> siprec@ietf.org<br><b>Subject:</b> Re: [si=
prec] SIPREC Interim - Would you attend in San Jose.<o:p></o:p></span></p><=
/div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D'>Hi All,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'>I have only had a very limited =
response to this request and therefore I don&#8217;t think we can justify h=
aving a f2f interim co-located with the RTCWEB meeting.<o:p></o:p></span></=
p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNor=
mal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";colo=
r:#1F497D'>However there is an alternative and that would be co-locating wi=
th the CLUE meeting and having the meeting in the Boston area on the 17<sup=
>th</sup> of February. This would give us until the middle of January to ma=
ke a final decision and to make some progress via the mailing list. Lets ki=
ck start some more discussion on the list there are a number of IETF82 acti=
ons that need further discussion.<o:p></o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I will also=
 create a doodle poll to see who would commit to an interim meeting in Bost=
on.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'>Regards<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"=
;color:#1F497D'>Andy<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMso=
Normal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";c=
olor:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p=
>&nbsp;</o:p></span></p><div style=3D'border:none;border-left:solid blue 1.=
5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none;border-top:so=
lid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>F=
rom:</span></b><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Ta=
homa","sans-serif"'> <a href=3D"mailto:siprec-bounces@ietf.org">siprec-boun=
ces@ietf.org</a> [<a href=3D"mailto:siprec-bounces@ietf.org">mailto:siprec-=
bounces@ietf.org</a>] <b>On Behalf Of </b>Hutton, Andrew<br><b>Sent:</b> 09=
 December 2011 16:34<br><b>To:</b> <a href=3D"mailto:siprec@ietf.org">sipre=
c@ietf.org</a><br><b>Subject:</b> [siprec] SIPREC Interim - Would you atten=
d in San Jose.<br><b>Importance:</b> High<o:p></o:p></span></p></div></div>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span s=
tyle=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>Hi All,<o:p></=
o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.=
0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><=
div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Calib=
ri","sans-serif"'>It looks like RTCWEB will be having a face to face interi=
m in San Jose on the 31</span><sup><span style=3D'font-size:7.5pt;font-fami=
ly:"Calibri","sans-serif"'>st</span></sup><span style=3D'font-size:10.0pt;f=
ont-family:"Calibri","sans-serif"'> Jan and 1</span><sup><span style=3D'fon=
t-size:7.5pt;font-family:"Calibri","sans-serif"'>st</span></sup><span style=
=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'> of Feb 2012 there=
 will I believe be at least some people attending this who are active in SI=
PREC.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p></o:p></span=
></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-f=
amily:"Calibri","sans-serif"'>If we could arrange a SIPREC interim at the s=
ame location on the 2</span><sup><span style=3D'font-size:7.5pt;font-family=
:"Calibri","sans-serif"'>nd</span></sup><span style=3D'font-size:10.0pt;fon=
t-family:"Calibri","sans-serif"'> of February would you attend in person?<o=
:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-siz=
e:10.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p></o:p></span></p></=
div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"=
Calibri","sans-serif"'>Please let me know by the 16</span><sup><span style=
=3D'font-size:7.5pt;font-family:"Calibri","sans-serif"'>th</span></sup><spa=
n style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'> of Decembe=
r if there is at least a high probability of you attending such a SIPREC in=
terim.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'=
font-size:10.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p></o:p></spa=
n></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-=
family:"Calibri","sans-serif"'>Regards<o:p></o:p></span></p></div><div><p c=
lass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Calibri","san=
s-serif"'>Andy<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span s=
tyle=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p></o=
:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.0=
pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><d=
iv><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Calibr=
i","sans-serif"'>&nbsp;<o:p></o:p></span></p></div></div></div></div></body=
></html>=

--_000_101C6067BEC68246B0C3F6843BCCC1E311FD739527MCHP058Agloba_--

From andrew.hutton@siemens-enterprise.com  Sun Dec 18 13:29:34 2011
Return-Path: <andrew.hutton@siemens-enterprise.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 769A521F8AE9 for <siprec@ietfa.amsl.com>; Sun, 18 Dec 2011 13:29:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level: 
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xCx+ZeBY4wvb for <siprec@ietfa.amsl.com>; Sun, 18 Dec 2011 13:29:33 -0800 (PST)
Received: from senmx11-mx.siemens-enterprise.com (senmx11-mx.siemens-enterprise.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6B07821F8AD2 for <siprec@ietf.org>; Sun, 18 Dec 2011 13:29:33 -0800 (PST)
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx.siemens-enterprise.com (Server) with ESMTP id C0D6C1EB8411 for <siprec@ietf.org>; Sun, 18 Dec 2011 22:29:30 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Sun, 18 Dec 2011 22:29:30 +0100
From: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Sun, 18 Dec 2011 22:29:46 +0100
Thread-Topic: Doodle Poll -  SIPREC Interim - Boston Area, Feb 17th 2012
Thread-Index: Acy2kF4m4Fu11k7CS7uNQ8B5GkBYBAFeu3pgAGyVRzAAA58OwA==
Message-ID: <101C6067BEC68246B0C3F6843BCCC1E311FD739529@MCHP058A.global-ad.net>
References: <101C6067BEC68246B0C3F6843BCCC1E311FAE710C2@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E311FD73943D@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E311FD739527@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311FD739527@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_101C6067BEC68246B0C3F6843BCCC1E311FD739529MCHP058Agloba_"
MIME-Version: 1.0
Subject: [siprec] Doodle Poll -  SIPREC Interim - Boston Area, Feb 17th 2012
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Dec 2011 21:29:34 -0000

--_000_101C6067BEC68246B0C3F6843BCCC1E311FD739529MCHP058Agloba_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

I created a doodle poll to register an indication of whether or not you wou=
ld attend a face to face SIPREC Interim meeting if it was held in the Bosto=
n (US) area on the 17th of February (i.e. day after the CLUE meeting).  The=
 venue for such a meeting would most likely be the same as for the CLUE mee=
ting (i.e. Polycom office in Andover, MA) unless we get a large number of p=
eople.

Remote participation would be possible but this poll is for the purpose of =
understanding who would actually attend in person.



http://www.doodle.com/q3555taia7xbpmt2



This poll will close on the 6th of January after which the chairs will make=
 a decision as to whether the meeting should take place.

Regards
Andy


--_000_101C6067BEC68246B0C3F6843BCCC1E311FD739529MCHP058Agloba_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi All,<o=
:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fo=
nt-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif";color:#1F497D'>I created a doodle poll to register an indicat=
ion of whether or not you would attend a face to face SIPREC Interim meetin=
g if it was held in the Boston (US) area on the 17<sup>th</sup> of February=
 (i.e. day after the CLUE meeting).&nbsp; The venue for such a meeting woul=
d most likely be the same as for the CLUE meeting (i.e. Polycom office in A=
ndover, MA) unless we get a large number of people.<o:p></o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'>Remote participation would be possible but this poll is for the purp=
ose of understanding who would actually attend in person.<o:p></o:p></span>=
</p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>=
<p class=3DMsoPlainText><span lang=3DEN-US><a href=3D"http://www.doodle.com=
/q3555taia7xbpmt2">http://www.doodle.com/q3555taia7xbpmt2</a><o:p></o:p></s=
pan></p><p class=3DMsoPlainText><span lang=3DEN-US><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoPlainText><span lang=3DEN-US>This poll will close on the =
6<sup>th</sup> of January after which the chairs will make a decision as to=
 whether the meeting should take place.<o:p></o:p></span></p><p class=3DMso=
Normal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";c=
olor:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Rega=
rds<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'>Andy<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calib=
ri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p></div></body></=
html>=

--_000_101C6067BEC68246B0C3F6843BCCC1E311FD739529MCHP058Agloba_--

From pravindran@sonusnet.com  Fri Dec 23 09:15:02 2011
Return-Path: <pravindran@sonusnet.com>
X-Original-To: siprec@ietfa.amsl.com
Delivered-To: siprec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA8EF21F85A8 for <siprec@ietfa.amsl.com>; Fri, 23 Dec 2011 09:15:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ti0s1gD-HIR for <siprec@ietfa.amsl.com>; Fri, 23 Dec 2011 09:15:02 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id BDE6221F8AF5 for <siprec@ietf.org>; Fri, 23 Dec 2011 09:15:01 -0800 (PST)
Received: from sonusmail05.sonusnet.com (sonusmail05.sonusnet.com [10.128.32.155]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pBNHFfk9022034;  Fri, 23 Dec 2011 12:15:41 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail05.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 23 Dec 2011 12:15:00 -0500
Received: from INBA-HUB02.sonusnet.com ([10.70.51.87]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 23 Dec 2011 22:45:39 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub02.sonusnet.com ([fe80::80b9:dc60:caf7:7dfc%11]) with mapi id 14.01.0339.001; Fri, 23 Dec 2011 22:45:38 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>, "siprec@ietf.org" <siprec@ietf.org>
Thread-Topic: CNAME attribute in participant metadata element [was RE: IETF 82 Minutes.]
Thread-Index: AQHMwZZ9GaMczMqmT0qGBx+j73zrGA==
Date: Fri, 23 Dec 2011 17:15:38 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C01DAEE64@inba-mail01.sonusnet.com>
References: <101C6067BEC68246B0C3F6843BCCC1E311FAE70EB6@MCHP058A.global-ad.net>
In-Reply-To: <101C6067BEC68246B0C3F6843BCCC1E311FAE70EB6@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [121.242.142.186]
Content-Type: multipart/alternative; boundary="_000_387F9047F55E8C42850AD6B3A7A03C6C01DAEE64inbamail01sonus_"
MIME-Version: 1.0
X-OriginalArrivalTime: 23 Dec 2011 17:15:39.0540 (UTC) FILETIME=[7E511540:01CCC196]
Subject: [siprec] CNAME attribute in participant metadata element [was RE: IETF 82 Minutes.]
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Dec 2011 17:15:02 -0000

--_000_387F9047F55E8C42850AD6B3A7A03C6C01DAEE64inbamail01sonus_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

As per IETF-82 meeting, we need to discuss in detail whether CNAME attribut=
e has to be part of participant metadata element. The initial idea is to ma=
p CNAME to participant id but it is complicated in some of the cases as men=
tioned in IETF-82. I attached the relevant IETF-82 discussion as a note of =
this mail. Let us discuss in this mail thread for the need of CNAME attribu=
te and the issues related to it.

Thanks
Partha


Note:
Open Item: Metadata Model: Participant / Carry CNAME as participant attribu=
te
Any objections to having a new attribute in Participant class to represent =
CNAME? This could be useful, but might not work in more complicated cases (=
e.g. recordings of conferences).

Paul: You need something.
Magnus: It is a good idea but maybe not the main use case at the moment.
Hadriel: Could have two different CNAMEs for the same endpoint if they are =
not sync so not a participant identifier.
Ram: Useful for correlation
Charles: We are not using it as participant ID, but could be used to map to=
 a participant.
Paul: It can get complicated
Brian: Doesn't mean we can't try
Hadriel: Can hurt if people expect this information
Brian: We aren't chartered to come up with identifier for multiple devices =
or users
Hadriel: This is not really a solution to this problem
Paul: Defer this as it needs more investigation
Charles:
Andy: Needs more discussion



From: siprec-bounces@ietf.org [mailto:siprec-bounces@ietf.org] On Behalf Of=
 Hutton, Andrew
Sent: Friday, December 09, 2011 5:28 PM
To: siprec@ietf.org
Subject: [siprec] IETF 82 Minutes.

SIPREC IETF82 minutes can be found at http://www.ietf.org/proceedings/82/mi=
nutes/siprec.txt.

Any issues with these then please let me know and I will check against the =
audio and correct if necessary.

Lets kick start some discussion on the open issues since we have all had a =
few weeks now to recover after Taipei.

Regards
Andy


--_000_387F9047F55E8C42850AD6B3A7A03C6C01DAEE64inbamail01sonus_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Hi all,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">As per IETF-82 meeting, we need to discuss in detail wheth=
er CNAME attribute has to be part of participant metadata element. The init=
ial idea is to map CNAME to participant id but
 it is complicated in some of the cases as mentioned in IETF-82. I attached=
 the relevant IETF-82 discussion as a note of this mail. Let us discuss in =
this mail thread for the need of CNAME attribute and the issues related to =
it.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Thanks<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Partha<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Note:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Open Item: Metadata Model: Participant / Carry CNAME as pa=
rticipant attribute<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Any objections to having a new attribute in Participant cl=
ass to represent CNAME? This could be useful, but might not work in more co=
mplicated cases (e.g. recordings of conferences).
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Paul: You need something.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Magnus: It is a good idea but maybe not the main use case =
at the moment.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Hadriel: Could have two different CNAMEs for the same endp=
oint if they are not sync so not a participant identifier.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Ram: Useful for correlation<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Charles: We are not using it as participant ID, but could =
be used to map to a participant.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Paul: It can get complicated<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Brian: Doesn't mean we can't try<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Hadriel: Can hurt if people expect this information<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Brian: We aren't chartered to come up with identifier for =
multiple devices or users<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Hadriel: This is not really a solution to this problem<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Paul: Defer this as it needs more investigation<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Charles:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Andy: Needs more discussion<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> siprec-b=
ounces@ietf.org [mailto:siprec-bounces@ietf.org]
<b>On Behalf Of </b>Hutton, Andrew<br>
<b>Sent:</b> Friday, December 09, 2011 5:28 PM<br>
<b>To:</b> siprec@ietf.org<br>
<b>Subject:</b> [siprec] IETF 82 Minutes.<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">SIPREC IETF82 minutes can be found at
<a href=3D"http://www.ietf.org/proceedings/82/minutes/siprec.txt">http://ww=
w.ietf.org/proceedings/82/minutes/siprec.txt</a><b>.</b><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Any issues with these then please let m=
e know and I will check against the audio and correct if necessary.<o:p></o=
:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Lets kick start some discussion on the =
open issues since we have all had a few weeks now to recover after Taipei.<=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Regards<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Andy<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>

--_000_387F9047F55E8C42850AD6B3A7A03C6C01DAEE64inbamail01sonus_--
