IETF Logo Mail Archive

Re: [sipcore] Change log for 4028bis

Samir Srivastava <srivastava_samir@hush.com> Thu, 14 May 2020 14:05 UTC

Return-Path: <srivastava_samir@hush.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C116F3A0A63 for <sipcore@ietfa.amsl.com>; Thu, 14 May 2020 07:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hush.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 089wFl6_LalT for <sipcore@ietfa.amsl.com>; Thu, 14 May 2020 07:05:35 -0700 (PDT)
Received: from smtp10.hushmail.com (smtp10a.hushmail.com [65.39.178.239]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C2AA3A0A67 for <sipcore@ietf.org>; Thu, 14 May 2020 07:05:35 -0700 (PDT)
Received: from smtp10.hushmail.com (localhost [127.0.0.1]) by smtp10.hushmail.com (Postfix) with SMTP id DC5B0C032A for <sipcore@ietf.org>; Thu, 14 May 2020 14:05:34 +0000 (UTC)
X-hush-tls-connected: 1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=hush.com; h=date:to:subject:from; s=hush; bh=FnMLuvnBykrRGQl3HaDXqzSYW+J/N0rChbL8NCG3syY=; b=A/NCKMlpJe3tlLapoR8LMpb8RkZNtJGx8/jcCFSPE0pNVCb12MQCwrGEqtMmW00NsU7IuL3spWuAXMi4F2JKyXjUYlMT+VMCC3E0uUTMQAvgB6C/9gFD1xbYlYFyyDSnjAV8DEeRwvxKzaaKU9mB2zaKnn5zyDEmi35eF373AMtwSkh+O7OHD6Eg7IbFlJh9uH33iOxxFxB/RCY7XQl1HiE67uzRq87IVmnAEb+OJhc7CJ7PhewDCCMjkS+6SrLE2MgcidgHCrjQ0woRaUsT7f3xlBNnjNq/Y56deCwbzAiDujj4/i3jamJCeE5CwLlr45Ymsv+0u5MVuEWfpE/rIQ==
Received: from smtp.hushmail.com (w7.hushmail.com [65.39.178.32]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp10.hushmail.com (Postfix) with ESMTPS; Thu, 14 May 2020 14:05:34 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99) id 2BE5640685; Thu, 14 May 2020 14:05:34 +0000 (UTC)
MIME-Version: 1.0
Date: Thu, 14 May 2020 20:05:33 +0600
To: Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org>, sipcore@ietf.org
From: Samir Srivastava <srivastava_samir@hush.com>
In-Reply-To: <0251C7EB-240A-4F8E-A510-E5884ADE6265@ericsson.com>
References: <20200510131235.8E2A6C0171@smtp.hushmail.com> <854d7cef-03eb-8974-9159-c493df015996@alum.mit.edu> <8414733e-a5d9-2502-6a89-d6460d931be9@ntlworld.com> <20200511153943.792F620111@smtp.hushmail.com> <32547453-1350-b8a2-d7a5-fc253cf3eaf4@ntlworld.com> <20200512105430.7F9542011C@smtp.hushmail.com> <c12508c3-11c2-aa14-28c6-ecfea4b73bd5@ntlworld.com> <20200514120351.EEBD6406C0@smtp.hushmail.com> <0251C7EB-240A-4F8E-A510-E5884ADE6265@ericsson.com>
Content-Type: multipart/alternative; boundary="=_ef9b3ad61e87bed205b9273d40ff0666"
Message-Id: <20200514140534.2BE5640685@smtp.hushmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/CAHu0KnSpA8nlmVbvskYwRywuYk>
Subject: Re: [sipcore] Change log for 4028bis
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2020 14:05:39 -0000

Hi,
  Suppose I support RFC 4028, And I want to support your new RFC which
is in bis form now. Instead of going through the  minute details of
your new RFC as a whole, I focus on the changes done in the new RFC
with respect to 4028. 
  I am looking something similar to Chapter 28 of RFC 3261. Where it
lists the details of changes done with respect earlier SIP RFC 2543.
  Thanks
   Samir Srivastava
   http://samirsrivastava.typepad.com
On 5/14/2020 at 7:24 PM, "Christer Holmberg"  wrote:      

	Hi, 
	I am not sure I understand what you mean by “provide the changes
with respect to RFC 4028”. 
	Regards, 
	Christer 
	From: sipcore  on behalf of Samir Srivastava 
 Date: Thursday, 14 May 2020 at 15.04
 To: "sipcore@ietf.org" 
 Subject: [sipcore] Change log for 4028bis   
	Hi,   
	  4028bis should provide the changes done with respect to RFC 4028.
Like RFC 3261 provide changes done with respect 2543.   
	Thanks    
	Samir Srivastava   
	http://samirsrivastava.typepad.com

v2.23.0 | Report a Bug | By Email