Re: [Insipid] I-D Action: draft-ietf-insipid-logme-reqs-10.txt

"Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com> Tue, 25 October 2016 17:06 UTC

Return-Path: <gsalguei@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 6A85D1296C4 for <insipid@ietfa.amsl.com>; Tue, 25 Oct 2016 10:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.952
X-Spam-Level:
X-Spam-Status: No, score=-14.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, SPF_PASS=-0.001, 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 tbsvZLLRsDlL for <insipid@ietfa.amsl.com>; Tue, 25 Oct 2016 10:06:27 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 512BE1295BD for <insipid@ietf.org>; Tue, 25 Oct 2016 10:06:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3868; q=dns/txt; s=iport; t=1477415187; x=1478624787; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=CUgJ9c8JBAMs6yQROPM9k9dl+Yh24YxaJ4f2JTgBLKw=; b=NtW3bA2nUVaXFYrE5NjtTaWUn+hsMohqmx6A4oWvSVHW+ORLjy72iIfv SpAyVWMbT0nWyQ9cz/jdFc42Or410egSpj6wVzwCcZoYxBQBbZYu4kOQ8 MDoE8pwomtEIFFDKrNcba9pYMyChw3+5naAQT2ViBUuL6Ox9W6vFGBO8l w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CCAQDAjw9Y/4QNJK1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgy8BAQEBAR1YbRAHjS6WfpQ/ggccC4JEgmxKAhqBVz8UAQIBAQEBAQE?= =?us-ascii?q?BYiiEYgEBAQMBAQEBIBEzBwsFCwIBCBgCAiYCAgIlCxUQAgQOBRuIMAgOtQqMe?= =?us-ascii?q?AEBAQEBAQEBAQEBAQEBAQEBAQEBARyBB4U2gX0IglCEOg2DBCyCLwWaFgGGKYl?= =?us-ascii?q?tgW5OhB+JKIcZhW+EAAEeNl6FAnKFZIEtgQABAQE?=
X-IronPort-AV: E=Sophos;i="5.31,546,1473120000"; d="scan'208";a="166623123"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 25 Oct 2016 17:06:26 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u9PH6P1R018391 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 25 Oct 2016 17:06:25 GMT
Received: from xch-aln-009.cisco.com (173.36.7.19) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 25 Oct 2016 12:06:24 -0500
Received: from xch-aln-009.cisco.com ([173.36.7.19]) by XCH-ALN-009.cisco.com ([173.36.7.19]) with mapi id 15.00.1210.000; Tue, 25 Oct 2016 12:06:24 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: "Arun Arunachalam (carunach)" <carunach@cisco.com>
Thread-Topic: [Insipid] I-D Action: draft-ietf-insipid-logme-reqs-10.txt
Thread-Index: AQHSLsOCLyR9IhyoykW6SrU5rHKt5qC5gH+AgAA6BAA=
Date: Tue, 25 Oct 2016 17:06:24 +0000
Message-ID: <21C99A14-6005-45BF-9743-5958D4EFCE03@cisco.com>
References: <147740203053.15121.3736129154025141318.idtracker@ietfa.amsl.com> <B16F5D38-9CCD-4585-B681-09DC6B800772@cisco.com>
In-Reply-To: <B16F5D38-9CCD-4585-B681-09DC6B800772@cisco.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.82.252.140]
Content-Type: text/plain; charset="utf-8"
Content-ID: <4C8DE0AC30BE034DAB2917D94AC10FD9@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/LdyXzLPk79spqsHknbCQkrUPRs4>
Cc: "Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com>, "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] I-D Action: draft-ietf-insipid-logme-reqs-10.txt
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 25 Oct 2016 17:06:31 -0000

Hi Authors - 

Thanks you for the update.  I have requested publication.

Let’s work on finishing off the logme solution draft next.

Cheers,

Gonzalo


> On Oct 25, 2016, at 6:38 AM, Arun Arunachalam (carunach) <carunach@cisco.com> wrote:
> 
> Hi Folks,
> 
> We have posted a new version to address issues identified by Idnits tools
> 
> Thanks!
> Peter & Arun
> 
> 
>> On Oct 25, 2016, at 9:27 AM, internet-drafts@ietf.org wrote:
>> 
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the INtermediary-safe SIP session ID of the IETF.
>> 
>>        Title           : Requirements for Marking SIP Messages to be Logged
>>        Authors         : Peter Dawes
>>                          Chidambaram Arunachalam
>> Filename        : draft-ietf-insipid-logme-reqs-10.txt
>> Pages           : 10
>> Date            : 2016-10-25
>> 
>> Abstract:
>>   SIP networks use signaling monitoring tools to debug customer
>>   reported problems and for regression testing if network or client
>>   software is upgraded.  As networks grow and become interconnected,
>>   including connection via transit networks, it becomes impractical to
>>   predict the path that SIP signaling will take between clients, and
>>   therefore impractical to monitor SIP signaling end-to-end.
>> 
>>   This draft describes requirements for adding an indicator to the SIP
>>   protocol data unit (PDU, or a SIP message) that marks the PDU as a
>>   candidate for logging.  Such marking will typically be applied as
>>   part of network testing controlled by the network operator and not
>>   used in regular client signaling.  However, such marking can be
>>   carried end-to-end including the SIP terminals, even if a session
>>   originates and terminates in different networks.
>> 
>> 
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-insipid-logme-reqs/
>> 
>> There's also a htmlized version available at:
>> https://tools.ietf.org/html/draft-ietf-insipid-logme-reqs-10
>> 
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-insipid-logme-reqs-10
>> 
>> 
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> _______________________________________________
>> insipid mailing list
>> insipid@ietf.org
>> https://www.ietf.org/mailman/listinfo/insipid
> 
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid