Re: [Sipping] Offer/answer LS: How to document it

Takuya Sawada <tu-sawada@kddi.com> Fri, 08 August 2008 11:26 UTC

Return-Path: <sipping-bounces@ietf.org>
X-Original-To: sipping-archive@optimus.ietf.org
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 856F03A69F4; Fri, 8 Aug 2008 04:26:26 -0700 (PDT)
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99AC33A6850 for <sipping@core3.amsl.com>; Fri, 8 Aug 2008 04:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
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 Nia3OsHDIS8Z for <sipping@core3.amsl.com>; Fri, 8 Aug 2008 04:26:24 -0700 (PDT)
Received: from UTMC1102.kddi.com (athena.kddi.com [210.141.112.39]) by core3.amsl.com (Postfix) with ESMTP id 64C133A6822 for <sipping@ietf.org>; Fri, 8 Aug 2008 04:26:24 -0700 (PDT)
Received: from UTMC1133 (unknown [10.5.16.198]) by UTMC1102.kddi.com (Postfix) with SMTP id 71B582715; Fri, 8 Aug 2008 20:26:23 +0900 (JST)
Received: from localhost (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with SMTP id ECBB31A17; Fri, 8 Aug 2008 20:26:20 +0900 (JST)
Received: from UTMC1114.kddi.com (unknown [10.5.16.17]) by UTMC1123.kddi.com (Postfix) with ESMTP id C11221C42; Fri, 8 Aug 2008 20:26:14 +0900 (JST)
Received: from KDDI-0803PC0335 ([10.200.209.235] [10.200.209.235]) by post-ims.kddi.com with ESMTPA; Fri, 8 Aug 2008 20:26:14 +0900
To: christer.holmberg@ericsson.com, pkyzivat@cisco.com
From: Takuya Sawada <tu-sawada@kddi.com>
References: <BBE61D1553D8A34F812FF87377B2935F04696B21@ATL1VEXC020.usdom003.tco.tc> <CA9998CD4A020D418654FCDEF4E707DF046C78D9@esealmw113.eemea.ericsson.se> <489B5756.3000301@cisco.com> <CA9998CD4A020D418654FCDEF4E707DF046C78DB@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF046C78DB@esealmw113.eemea.ericsson.se>
Message-Id: <200808082026.DEI00589.EXUVBBTBt@kddi.com>
X-Mailer: Winbiff [Version 2.50]
X-Accept-Language: ja,en
Date: Fri, 08 Aug 2008 20:26:14 +0900
Mime-Version: 1.0
X-WAuditID: 0808082026210000314474
Cc: sipping@ietf.org, brett@broadsoft.com
Subject: Re: [Sipping] Offer/answer LS: How to document it
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

Hi,

I think I would also agree to hold it to reflect the fixes.

Regards,
Takuya

> 
> Hi,
> 
> >I agree that the goal is to clarify rather than fix. As such it probably 
> >doesn't need to move.
> >
> >But the clarification would be better if it didn't have open issues.
> >
> >One solution is to simply hold this as a draft pending the fixes, and 
> >then rev it to reflect the fixes before progressing it.
> >
> >OR, we could simply let it progress with the open issues.
> >
> >Much as I would like to see it done, I am leaning toward holding it.
> 
> I think I would agree. A clarification document with open issues is a little strange :)
> 
> Because, apart from the remaining open issues, the draft is very stable, and people can use it.
> 
> The main open issue still remaining is the one related to how-to-reject-offers-in-PRACK. There are a number of different solution proposals, each with pros and cons, and I think we will eventually just have to pick one. Again, from an interop perspective it's better to know how things shall work, and take the consequences based on that, than having no idea on how things should work - or having many different opinions on how things should work...
> 
> I've started to put together a draft regarding the PRACK issue. The intention is not to produce an RFC, but to have somewhere to document the different alternatives etc during the work on finding a solution.
> 
> Regards,
> 
> Christer
> 
> 
> 
> 	Thanks,
> 	Paul
> 
> Christer Holmberg wrote:
> > Hi,
> > 
> > I don't think we need to move the offer/answer draft to the SIP WG.
> > 
> > The purpose of the draft is simply to clarify, not to specify protocol procedures. That is why I said that even if we document the decission regarding the re-INVITE fallback issue in the offer/answer draft, in addition we still need to also document it in some normative SIP document.
> > 
> > Regards,
> > 
> > Christer
> > 
> > 
> > 
> > 
> > -----Alkuper臺nen viesti-----
> > L臧ett臻・ Brett Tate [mailto:brett@broadsoft.com]
> > L臧etetty: to 7.8.2008 19:53
> > Vastaanottaja: Christer Holmberg; sipping LIST
> > Aihe: RE: [Sipping] Offer/answer LS: How to document it
> >  
> >> Is it too late to get it into draft-ietf-sipping-sip-offeranswer, 
> >> where it is still listed as an open issue (in addtion we of 
> >> course also needs to get it into normative text)?
> > 
> > Draft-ietf-sipping-sip-offeranswer currently has several open issues.
> > If there are to be normative updates to the SIP RFCs, it should likely
> > occur within the SIP WG.  Additionally, I'd prefer all the open issues
> > mentioned within draft-ietf-sipping-sip-offeranswer be addressed at the
> > same time.  I have no preference between 1) allowing
> > draft-ietf-sipping-sip-offeranswer to proceed with open issues or 2)
> > moving the draft to the SIP working group so the open issues can be
> > resolved.
> > 
> > _______________________________________________
> > Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> > 
> 
> _______________________________________________
> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

--------
Takuya Sawada
KDDI Corporation (KDDI)
Garden Air Tower, 3-10-10, Iidabashi, 
Chiyoda-ku, Tokyo 102-8460, Japan
Tel: +81-3-6678-2997
Fax: +81-3-6678-0286
tu-sawada@kddi.com

------------------------------------------------------------------
注意:この電子メールには、KDDI株式会社の機密情報が含まれている
      場合が有ります。正式なメール受信者でない場合、メール複製、
   再配信または情報の使用を固く禁じております。
      エラー、手違い等でこのメールを受け取られましたら、お手数を
   おかけ致しますが、削除を行い配信者に連絡をお願い致します。
NOTE: This electronic mail message may contain confidential and
   privileged information from KDDI Corporation. If you are
   not the intended recipient, any disclosure, photocopying,
      distribution or use of the contents of the received
      information is prohibited. If you have received this e-mail
      in error, please notify the sender immediately and
     permanently delete this message and all related copies.
-------------------------------------------------------------------

_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP