IETF Logo Mail Archive

Re: [sipcore] Call for Adoptions: Drafts for new milestones

"DOLLY, MARTIN C" <md3135@att.com> Mon, 16 January 2017 16:38 UTC

Return-Path: <md3135@att.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 7317312959E for <sipcore@ietfa.amsl.com>; Mon, 16 Jan 2017 08:38:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 g2fL7ze8Fpbq for <sipcore@ietfa.amsl.com>; Mon, 16 Jan 2017 08:38:44 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 4D1BD1294D6 for <sipcore@ietf.org>; Mon, 16 Jan 2017 08:38:44 -0800 (PST)
Received: from pps.filterd (m0083689.ppops.net [127.0.0.1]) by m0083689.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v0GGZY5K032146; Mon, 16 Jan 2017 11:38:41 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0083689.ppops.net-00191d01. with ESMTP id 280n4fjex2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 16 Jan 2017 11:38:40 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v0GGcdBM031784; Mon, 16 Jan 2017 11:38:40 -0500
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v0GGcYeL031708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Jan 2017 11:38:35 -0500
Received: from MISOUT7MSGHUBAG.ITServices.sbc.com (MISOUT7MSGHUBAG.itservices.sbc.com [130.9.129.151]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Mon, 16 Jan 2017 16:38:21 GMT
Received: from MISOUT7MSGUSRDB.ITServices.sbc.com ([169.254.2.18]) by MISOUT7MSGHUBAG.ITServices.sbc.com ([130.9.129.151]) with mapi id 14.03.0319.002; Mon, 16 Jan 2017 11:38:20 -0500
From: "DOLLY, MARTIN C" <md3135@att.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Adam Roach <adam@nostrum.com>, 'SIPCORE' <sipcore@ietf.org>, Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Thread-Topic: [sipcore] Call for Adoptions: Drafts for new milestones
Thread-Index: AQHSbTdm0E02YJFp00GoTEcPhv1fDKE252CwgARr+cA=
Date: Mon, 16 Jan 2017 16:38:20 +0000
Message-ID: <E42CCDDA6722744CB241677169E836564ABC18D5@MISOUT7MSGUSRDB.ITServices.sbc.com>
References: <f2302527-04e0-3764-8572-8e9bef2dd769@nostrum.com> <7594FB04B1934943A5C02806D1A2204B4BF73276@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BF73276@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.142.93]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-01-16_14:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1701160242
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/A8U_kXyUCbZhtehlXKEGR-6zxjI>
Subject: Re: [sipcore] Call for Adoptions: Drafts for new milestones
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 16 Jan 2017 16:38:45 -0000

I support its adoption.

-----Original Message-----
From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: Friday, January 13, 2017 4:11 PM
To: Adam Roach <adam@nostrum.com>; 'SIPCORE' <sipcore@ietf.org>; Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Subject: Re: [sipcore] Call for Adoptions: Drafts for new milestones

Hi,

In addition, I'd like to consider adopting:

https://datatracker.ietf.org/doc/draft-yusef-sipcore-sip-authn/

As indicated by Rifaat, while THIS draft was just submitted, it's related to an topic that we have already discussed in the past. Based on discussions with e.g., Jon Peterson, the controversial parts of the previous suggestion has been removed from the new draft.

Regards,

Christer


-----Original Message-----
From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of Adam Roach
Sent: 13 January 2017 02:52
To: 'SIPCORE' <sipcore@ietf.org>
Subject: [sipcore] Call for Adoptions: Drafts for new milestones

[as chair]

As I mentioned in an earlier message, we have new milestones for SIPCORE, many of which we hope to finish in the first half of the year. 
To that end, I'd like to call for adoption of the documents that prompted adding the milestones. To be specific:

We propose adopting draft-schulzrinne-sipcore-callinfo-spam for the milestone "mechanism for labeling the nature of SIP calls"

We propose adopting draft-holmberg-sipcore-content-id for the milestone "clarification of the use of Content-ID"

We propose adopting draft-sparks-sipcore-name-addr-guidance for the milestone "clarification of the use of name-addr"

I'll note that these document -- and in particular the last two -- have had significant discussion and feedback already. In particular, the author of draft-sparks-sipcore-name-addr-guidance indicates that he believes that document is "done" and basically ready for last call.

Please provide feedback regarding adoption of these documents by Friday, January 27. Thanks!

/a

_______________________________________________
sipcore mailing list
sipcore@ietf.org
https://www.ietf.org/mailman/listinfo/sipcore

_______________________________________________
sipcore mailing list
sipcore@ietf.org
https://www.ietf.org/mailman/listinfo/sipcore

v2.23.0 | Report a Bug | By Email