Re: [sipcore] draft-ietf-sipcore-callinfo-spam-02.txt

One possibility is for Henning to do a remote presentation in sipcore.  Time zone challenges of course.

Brian

> On Nov 1, 2017, at 11:21 AM, Adam Roach <adam@nostrum.com <mailto:adam@nostrum.com>> wrote:
> 
> I've looked over the groups meeting later in the week, and can't find another session that is likely to have the correct community of interest.
> 
> I've also looked over the changes to the document, and they seem entirely editorial (albeit with a change that technically does impact the wire protocol). It's not clear that there are any remaining open issues that would clearly benefit from face-to-face time. Henning: do you have some questions you specifically wanted to address in the meeting? Or did you just want to present a list of changes to give people an opportunity to object?
> 
> If the latter, I believe it should be pretty easy for the chairs to say: "We've renamed the 'spam' parameter to 'confidence', and made some other minor editorial improvements. Interested parties should comment on the list if they object." It's up to the chairs whether they want to couple this request with a WGLC.
> 
> /a
> 
>> From: Henning Schulzrinne <hgs@cs.columbia.edu <mailto:hgs@cs.columbia.edu>>
>> Subject: draft-ietf-sipcore-callinfo-spam-02.txt
>> Date: October 30, 2017 at 11:08:36 PM EDT
>> To: sipcore-chairs@ietf.org <mailto:sipcore-chairs@ietf.org>, Stir Chairs <stir-chairs@tools.ietf.org <mailto:stir-chairs@tools.ietf.org>>
>> Resent-From: <alias-bounces@ietf.org <mailto:alias-bounces@ietf.org>>
>> Resent-From: wg-alias-bounces@tools.ietf.org <mailto:wg-alias-bounces@tools.ietf.org>
>> Resent-To: housley@vigilsec.com <mailto:housley@vigilsec.com>, rjsparks@nostrum.com <mailto:rjsparks@nostrum.com>
>> Resent-To: stir-chairs@ietf.org <mailto:stir-chairs@ietf.org>
>> 
>> Brian & Jean:
>> 
>> I submitted draft-ietf-sipcore-callinfo-spam-02.txt, which addresses
>> comments I have received.
>> 
>> I will be in Singapore, but an obligation related to a grant proposal
>> makes me arrive Wednesday morning. If there was a need to discuss the
>> draft, I had kind of hoped that we could move any draft discussion to
>> STIR, since that seemed topically close and since it was meeting late
>> in the week as of the time when I booked my flight, but that option is
>> apparently gone. (I know that session scheduling is tough given the
>> various constraints, so I'm not complaining.)
>> 
>> In any event, I'd like to figure out how to wrap up the draft since
>> discussion seems to have died down.
>> 
>> Henning
>> 
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org <mailto:sipcore@ietf.org>
> https://www.ietf.org/mailman/listinfo/sipcore