Re: [Insipid] Adam Roach's No Objection on draft-ietf-insipid-logme-marking-12: (with COMMENT)

"Arun Arunachalam (carunach)" <carunach@cisco.com> Fri, 14 September 2018 19:47 UTC

Return-Path: <carunach@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3DB6130EA7; Fri, 14 Sep 2018 12:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 a2M6NB78RkvV; Fri, 14 Sep 2018 12:47:03 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD4EC130F0E; Fri, 14 Sep 2018 12:47:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16971; q=dns/txt; s=iport; t=1536954422; x=1538164022; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=aeSloGWa2v7rNjEYMwvho2xnoc9xUfgK5Kaob0iswdE=; b=eJw4+bE6IP1p6+QnNW5k3PUkC+05GGJosOyYR4nmfly+vbGdAgqUSule 90OsEuasx/ii/jjwr0oiVvBkZOAs8uR52joKV5DLO6nRpEdmx3eI2kahW 4jQsRxNsYoX1Ls4hC+LS7dfHJZLiClVtxshtXDixwfHJ4VYbmTb6V0o2B k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C6AACnD5xb/5BdJa1bGgEBAQEBAgE?= =?us-ascii?q?BAQEIAQEBAYFSgQ93gWQoCpglgWiWZoF6C4RsAoNeITYWAQMBAQIBAQJtKIU?= =?us-ascii?q?5BnkQAgEIPwcyFBECBA4FgyGBHmSmdYoJimgXggCBOQwTgkyBQYZvgiYCjUG?= =?us-ascii?q?FZ4kMCQKQEhePBZQdAhEUgSUkDCWBVXAVZQGCQYIxHI4Gb413gR4BAQ?=
X-IronPort-AV: E=Sophos;i="5.53,374,1531785600"; d="scan'208,217";a="452293778"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Sep 2018 19:47:01 +0000
Received: from XCH-ALN-008.cisco.com (xch-aln-008.cisco.com [173.36.7.18]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id w8EJl1DR005393 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 14 Sep 2018 19:47:01 GMT
Received: from xch-aln-015.cisco.com (173.36.7.25) by XCH-ALN-008.cisco.com (173.36.7.18) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 14 Sep 2018 14:47:01 -0500
Received: from xch-aln-015.cisco.com ([173.36.7.25]) by XCH-ALN-015.cisco.com ([173.36.7.25]) with mapi id 15.00.1395.000; Fri, 14 Sep 2018 14:47:01 -0500
From: "Arun Arunachalam (carunach)" <carunach@cisco.com>
To: Adam Roach <adam@nostrum.com>
CC: "Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com>, The IESG <iesg@ietf.org>, "draft-ietf-insipid-logme-marking@ietf.org" <draft-ietf-insipid-logme-marking@ietf.org>, "insipid@ietf.org" <insipid@ietf.org>, "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>, "insipid-chairs@ietf.org" <insipid-chairs@ietf.org>, "Arun Arunachalam (carunach)" <carunach@cisco.com>
Thread-Topic: [Insipid] Adam Roach's No Objection on draft-ietf-insipid-logme-marking-12: (with COMMENT)
Thread-Index: AQHUNPbFIRPOAVten0urdhrPedQ0GqTCo/gAgAAzRQCAIK9BAIANKYYAgAABRoA=
Date: Fri, 14 Sep 2018 19:47:00 +0000
Message-ID: <1EEADD8D-5731-477E-B39F-E7D0F325F757@cisco.com>
References: <153437875319.3073.15951759162383331116.idtracker@ietfa.amsl.com> <AM5PR0501MB24659A3566177F30C6B48623973E0@AM5PR0501MB2465.eurprd05.prod.outlook.com> <a9436eb5-8f8e-2795-0c8d-83ab3dd84b0b@nostrum.com> <AM5PR0501MB24652A98561FDA52551A4F1897010@AM5PR0501MB2465.eurprd05.prod.outlook.com> <78ba4459-a9fd-0eda-10f4-f01c0324b916@nostrum.com>
In-Reply-To: <78ba4459-a9fd-0eda-10f4-f01c0324b916@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.58.69]
Content-Type: multipart/alternative; boundary="_000_1EEADD8D5731477EB39FE7D0F325F757ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.18, xch-aln-008.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/D4UTzBPTZ2gIkRAuE1oDajPVON0>
Subject: Re: [Insipid] Adam Roach's No Objection on draft-ietf-insipid-logme-marking-12: (with COMMENT)
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Sep 2018 19:47:19 -0000

Thanks Adam!

We will incorporate the additional suggestions and publish a new draft version.

Thanks!
Peter and Arun

On Sep 14, 2018, at 3:42 PM, Adam Roach <adam@nostrum.com<mailto:adam@nostrum.com>> wrote:

Hi! Thanks, these all look like good resolutions to the issues I raised. I have a small handful of editorial nits (below). They're extremely minor, and all have to do with hyphenation of compound adjectives.

/a


On 9/6/18 5:42 AM, Dawes, Peter, Vodafone Group wrote:

   o  If a dialog is to be marked, the only way to initiate "log me"
      marking is at the dialog creating request (e.g.  SIP INVITE) sent

"...dialog-creating request..."

   o  If a "log me" aware endpoint or intermediary that is already "log

'If a "log me"-aware endpoint...'

   o  If a "log me" aware endpoint or intermediary that is not "log me"

'If a "log me"-aware endpoint...'


   o  By requesting header and session level privacy from SIP
      intermediaries using the Privacy header

"...header- and session-level privacy..."