Re: [sip-ops] SIP OPTIONS "ping"

"Paul E. Jones" <paulej@packetizer.com> Mon, 27 September 2010 14:22 UTC

Return-Path: <paulej@packetizer.com>
X-Original-To: sip-ops@core3.amsl.com
Delivered-To: sip-ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2DD953A6BAF; Mon, 27 Sep 2010 07:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.56
X-Spam-Level:
X-Spam-Status: No, score=-0.56 tagged_above=-999 required=5 tests=[AWL=-0.375, BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NPpm3lIhe4pq; Mon, 27 Sep 2010 07:22:55 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by core3.amsl.com (Postfix) with ESMTP id 5558E3A6AFF; Mon, 27 Sep 2010 07:22:50 -0700 (PDT)
Received: from sydney (rrcs-98-101-146-183.midsouth.biz.rr.com [98.101.146.183]) (authenticated bits=0) by dublin.packetizer.com (8.14.2/8.14.2) with ESMTP id o8REMX55015490 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 27 Sep 2010 10:22:40 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1285597361; bh=EAIgOvR9OHDtYz+v9rQ5qVsYDEM+38OhUHpSis12zU8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding; b=DHpHLOynSeTRvWq3GVX3L9rHPL6ccNk8IPtcdsHvXZLKx1DiDWvLzmpepebqJDgPm kUp3TS/elWzDfiuMkFkMBKgitSZ6EHe0qGbSPBcGzMHTn4Bu0il1A7X2odR60O0xKi Sl5NSGHOG+dhmt4ChUPuTXtFhIiCg73FakSp862Y=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Cullen Jennings'" <fluffy@cisco.com>, <dispatch@ietf.org>
Date: Mon, 27 Sep 2010 10:22:30 -0400
Message-ID: <020901cb5e4f$6fdb9540$4f92bfc0$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: ActeT2qZakrYB/OQSKO2MbpTvRC4zw==
Content-Language: en-us
X-Mailman-Approved-At: Mon, 27 Sep 2010 20:08:44 -0700
Cc: sip-ops@ietf.org, 'Hadriel Kaplan' <HKaplan@acmepacket.com>
Subject: Re: [sip-ops] SIP OPTIONS "ping"
X-BeenThere: sip-ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Operations <sip-ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-ops>, <mailto:sip-ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-ops>
List-Post: <mailto:sip-ops@ietf.org>
List-Help: <mailto:sip-ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-ops>, <mailto:sip-ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Sep 2010 14:22:57 -0000

Folks,

I just wanted to bring this draft to everyone's attention again.  What
should we do with it?  Should we modify this to be informational or pursue a
standards track draft?  Several have expressed an interest in seeing this go
forward in some form to help ensure better interoperability, but the list
has been fairly silent.

Here's the draft:
http://tools.ietf.org/html/draft-jones-sip-options-ping


Thanks,
Paul

> -----Original Message-----
> From: sip-ops-bounces@ietf.org [mailto:sip-ops-bounces@ietf.org] On Behalf
> Of Paul E. Jones
> Sent: Friday, August 13, 2010 12:37 AM
> To: 'Cullen Jennings'; dispatch@ietf.org
> Cc: sip-ops@ietf.org; 'Hadriel Kaplan'
> Subject: Re: [sip-ops] SIP OPTIONS "ping"
> 
> Cullen,
> 
> Thanks for the suggestion.
> 
> All,
> 
> Please see the note below.  We're seeking advice on how to proceed with
> the subject draft.
> 
> Paul
> 
> > -----Original Message-----
> > From: Cullen Jennings [mailto:fluffy@cisco.com]
> > Sent: Thursday, August 12, 2010 11:44 PM
> > To: Paul E. Jones
> > Cc: sip-ops@ietf.org; Hadriel Kaplan
> > Subject: Re: [sip-ops] SIP OPTIONS "ping"
> >
> >
> > I think you discuss how to move forward with this draft on dispatch
> > mailing list given that's the point of that list is help with problems
> > like this.
> >
> > On Aug 11, 2010, at 22:14 , Paul E. Jones wrote:
> >
> > > Folks,
> > >
> > > Gonzalo and I produced an Internet Draft aiming at trying to bring
> > > some
> > consistency to the way in which SIP user agents implement an OPTIONS
> > "ping" procedure.  It seems that a very large number of vendors do
> > this, but unfortunately, there seems to be little consistency.
> > >
> > > Initially, we positioned the document as a standards track RFC,
> > > since
> > this essentially builds on RFC 3261.  However, there was some pushback
> > from folks in the IETF for a variety of reasons, not the least of
> > which is the fact that there is no working group chartered to do the
> > work.  We don't feel this one draft warrants the creation of a working
> group.
> > >
> > > So, we've got three options we can consider:
> > > 1)      Forge ahead outside of a working group
> > > 2)      Change the status of the draft to Informational
> > > 3)      Forget about the draft and let every SIP device do it the way
> > they want, throwing hope of consistency out the window
> > >
> > > (Yeah, you can tell I prefer not to go for the third option.)
> > >
> > > In any case, I'd like to get feedback from the on the SIP operators
> > > and
> > SIP implementers lists.  Do you think it's worth trying to address
> > this issue?  If so, which option do you think we should pursue?
> > >
> > > Note that we're certainly open to feedback on the draft.  I'd prefer
> > > it
> > to have a few more "MUST" statements in the text, rather than "SHOULD".
> > But, we need to find that right balance:
> > > http://tools.ietf.org/html/draft-jones-sip-options-ping
> > >
> > > Paul
> > >
> > > _______________________________________________
> > > sip-ops mailing list
> > > sip-ops@ietf.org
> > > https://www.ietf.org/mailman/listinfo/sip-ops
> >
> >
> > Cullen Jennings
> > For corporate legal information go to:
> > http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> >
> 
> 
> _______________________________________________
> sip-ops mailing list
> sip-ops@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-ops