Re: [dispatch] draft-sunil-sankar-dispatch-sip-incr-00: comments and question

sunil sinha <sunilkumarsinha9@gmail.com> Thu, 30 June 2016 05:40 UTC

Return-Path: <sunilkumarsinha9@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9471112DA12 for <dispatch@ietfa.amsl.com>; Wed, 29 Jun 2016 22:40:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SZsGB6rkbiGM for <dispatch@ietfa.amsl.com>; Wed, 29 Jun 2016 22:40:54 -0700 (PDT)
Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2064912D9FB for <dispatch@ietf.org>; Wed, 29 Jun 2016 22:40:54 -0700 (PDT)
Received: by mail-vk0-x232.google.com with SMTP id u68so52845720vkf.2 for <dispatch@ietf.org>; Wed, 29 Jun 2016 22:40:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0EDLVPkv8jqe0/SksHKAapzhIGr9IfYedk8zRnGxFww=; b=Jk/DDIcgUoDZSHVqIraehVXiL3sHxxNgcvwS5sfZOGR3dVlbVsNHRqssoP+CtWz1iZ Zi2/eXnfxBEjwMn9om6TutUwY/he5+lLkRR5XNYhOQFNzEHttbq/+Ygk+R9qiZJxTl57 cUJkiHsf1n1t+D+zFpcG3Wsc9Q5pTN7XBJEF3j1Fs6LyVzewxFvHAJ72XKaqnOX7EDpA M+aIbJgyodw+FQ7h+Hv6+Rtn36USduRbN+E4gDWip/no+zRQS2bjKoBpJqbR1ikYK4Y7 I9cpRIVv4qjKeN4aQQuXlAV77Jqnd4aGSeoMt+bSFceqr6FEi0K5ZUqjj6F8+SkHPafI xrxQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0EDLVPkv8jqe0/SksHKAapzhIGr9IfYedk8zRnGxFww=; b=LgxcfUlB5spIPThh36TR2tEQVsi0sTEGMKKofDsCmYbOpVhW6CWW84lXJLYGCq1prC TygAb9/xQzItaVN4X7LeqtU//83AUOtZX22pp3Dzsk795NZsJLYVHiCZtyHGHL9OE9mf 9yHw6BU7Zs8OsnF2D7BpSnMifnaCdc/biYZJusisIOsbVjcfGTylZoFhjsuA2sHwar/b XbghbE2G5dEYvbzjyRG6fqBiji2y4QiKiu7OBbv9THIzWQERlPB2WpIjy5GYJK+MBtS5 YKggemQ38qJFdeWjTkpHcXA89uMJKhldZWq2VklD0igZBZ1SEGT+9pzowoDbyHEJNz79 sWTw==
X-Gm-Message-State: ALyK8tIKlflxnziXWwMsjRmTZLLZ69kqMUdtb50YbkHjHe1I9nxCO/8+CdJqpFmEFWSZ+Uj95urs0cwQjVD99g==
X-Received: by 10.176.3.114 with SMTP id 105mr5740890uat.122.1467265253198; Wed, 29 Jun 2016 22:40:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.73.202 with HTTP; Wed, 29 Jun 2016 22:40:52 -0700 (PDT)
In-Reply-To: <D954ABAD-A6A6-4158-88AE-F5D7AD4AB1EA@cisco.com>
References: <3dfdc76b723c199cf9ca5ed97cb2f16e@mail.gmail.com> <D954ABAD-A6A6-4158-88AE-F5D7AD4AB1EA@cisco.com>
From: sunil sinha <sunilkumarsinha9@gmail.com>
Date: Thu, 30 Jun 2016 11:10:52 +0530
Message-ID: <CAEqbTC5VDs+FCLD-Fp=VQg96fVs8uorQtcG_7+PNfYWJx+6NMw@mail.gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary="001a113d15d835525b0536785098"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/7GYANtoJs2fE0POANKoJkxpox4U>
Cc: DISPATCH list <dispatch@ietf.org>, "Sunil Kumar Sinha -X (sunsinha - SCARLET WIRELESS INDIA PRIVATE LIMITED at Cisco)" <sunsinha@cisco.com>
Subject: Re: [dispatch] draft-sunil-sankar-dispatch-sip-incr-00: comments and question
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2016 05:40:57 -0000

Hi,

I don't think at this point Cisco or anyone else plan to implement this
draft in their product.

Thanks & Regards
sunil

On Tue, Jun 28, 2016 at 7:32 PM, Cullen Jennings (fluffy) <fluffy@cisco.com>
wrote:

>
> Does Cisco or anyone else plan to implement this draft in their products?
> I’m skeptical this would improve performance over cached parsing approaches.
>
>
>
> > On Jun 13, 2016, at 9:51 PM, Brett Tate <brett@broadsoft.com> wrote:
> >
> > Hi,
> >
> > The following are a few comments concerning
> > draft-sunil-sankar-dispatch-sip-incr-00.
> >
> > Thanks,
> > Brett
> >
> > ------
> >
> > 1) The draft should clarify the relation to SHOULD and MUST within other
> > RFCs concerning header inclusion.  Section 6.1 appears to indicate that
> > you can ignore MUST statements within other RFCs concerning the need to
> > include a specific a header.  However, I'm currently unsure if section 4
> > next-to-last sentence supports or conflicts with that mandate.
> >
> > 2) You might want to reword section 4 to use normative language.
> >
> > 3) How would this draft interact with RFC 4028 from refresh -versus-
> > deactivation perspective?
> >
> > 4) How would this draft interact with draft-ietf-insipid-session-id since
> > the presence of the Session-ID is to help debug the call flow?
> >
> > 5) You should clarify that transaction specific headers such as
> Supported,
> > Require, Proxy-Require, and Content-Length need to be included again.
> >
> > _______________________________________________
> > dispatch mailing list
> > dispatch@ietf.org
> > https://www.ietf.org/mailman/listinfo/dispatch
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>