Re: [ippm] FW: New Version Notification for draft-brockners-opsawg-ioam-deployment-00.txt

"Ramesh Sivakolundu (sramesh)" <sramesh@cisco.com> Wed, 30 October 2019 21:13 UTC

Return-Path: <sramesh@cisco.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A639120825; Wed, 30 Oct 2019 14:13:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, SPF_PASS=-0.001, URIBL_BLOCKED=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 header.b=d5sStx8E; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=pV6aRsXc
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 aljlOVB3_BKq; Wed, 30 Oct 2019 14:13:00 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63388120103; Wed, 30 Oct 2019 14:13:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3938; q=dns/txt; s=iport; t=1572469980; x=1573679580; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=r0EHF1nubHFHMQtwYVlesriL5KLesX+MN2v70JMlf2E=; b=d5sStx8EE1bmdaOt7jl3PiGKo1Otm63vj7eACJxKv46r30sZ27dAMM3B 7iuMlRFTCdmStAohuqCOJm+BLO0OI43iTsEPVLShikuErTaJ8/qVfoLE7 JiHQEFjEBz6yz5HYJ9WG6pEgv5GVTBoieqD7Cix/BJiHCB6aq6v5H9RR+ o=;
IronPort-PHdr: 9a23:nwtMTxwS9zu3p9LXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YhSN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZueE0T+IeXqRyc7B89FElRi+iLzPA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B6AQCW+7ld/5xdJa1lHAEBAQEBBwEBEQEEBAEBgWwEAQELAYFKUAVsWCAECyoKhB6DRgOKdE6CEJdrglIDVAkBAQEMAQEYCwoCAQGEQAIXg08kNwYOAgMJAQEEAQEBAgEFBG2FNwyFUQEBAQEDAQEQEREMAQEsCQMLBgEIEQQBAQMCJgIEJQsVCAoEARIigwABgkYDLgECDKgUAoE4iGB1gTKCfgEBBYFIQYMOGIIXCYEOKAGMEBiBf4ERJx+CTD6CYgEBAgEBhG0ygiyPfYVgmBUKgiSHEI4hG4I8coZlj0uOQIgskSICBAIEBQIOAQEFgWgjgVhwFRohKgGCQQlHEBSBWYEtOIM7hRSFP3SBKIw2AYENAQE
X-IronPort-AV: E=Sophos;i="5.68,248,1569283200"; d="scan'208";a="656678370"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 30 Oct 2019 21:12:59 +0000
Received: from XCH-ALN-015.cisco.com (xch-aln-015.cisco.com [173.36.7.25]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x9ULCxMk019110 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 30 Oct 2019 21:12:59 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-015.cisco.com (173.36.7.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 30 Oct 2019 16:12:58 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 30 Oct 2019 16:12:58 -0500
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 30 Oct 2019 16:12:58 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=E9x217i7dRizDIyBUPpjnAfTVXDUUAXV9DjXRvNj3BTd7DQTsLIjw596GVfBsSjnKv+ShqBnD18Q5HVkRH0AsgbBB0b8KjjGwZS5L/qe2ULVitZvW2juRKYbuHc2bkCo2O12aDW6GhE3yVr/fkLzw+hCeSCKaf3n1KvWnnmqFOJkwFhtR1QYnW/aVyKymtymVO3phEhkotLuiTP5xJG/kOPjxQ5aPhTH7i9SLfpTvEYKTYBQ0QngN489feWNVrWL0FPv69Z0IiN8JQJ5yC/erFmHubZ0+SIHKuz+57LtBpN7CI56cit5K7PZb7l5VqkLK+ThMbSC3MuX8Tc23sG3gg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=r0EHF1nubHFHMQtwYVlesriL5KLesX+MN2v70JMlf2E=; b=mAivaycABN/X+ZrheCDUbCkfVHvgL4GvV4amIm4KRL5g/NkkkktwMSZ4nKp+fhxUs3sofwct6cZAQt6Q+1yctioxisgPY98tg+x6kOJs55kgsT+EZBRg8C7DuRuU9xC6XUl7jHNtv4PbVjtlmqnr83K4pA3B71J854wcPL0env5JNOxhfh1r0aWE8EnT99vuMO3HeYGJsBze7pMAwXBf9cfsHqllaLUaTMad8pRlEXjVplHKYCA6+bLUwf1rA1jTqqxCgbBlEmHTzOqTGqBClwMiKZCqm5EoMXyZA0fAE22T4BeX4M5/I1NDTX3Iy03aLZmoYY5GpGp3RIZqVMVT/A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=r0EHF1nubHFHMQtwYVlesriL5KLesX+MN2v70JMlf2E=; b=pV6aRsXcudp6xRlZAZRmcPlkmHNgWIQLzeQKYsd1W3HYJwMA2hN1kyEuThgcHfzPCCmAxKGMGekqBYcNYvRcEEdxvg64ABXL1Wdt+Tt71aDQ5RgZRhYr2unbipo8O3t9D+zjgmGLjP2EWfFRs01ttcHFEZfdCZfFxj8a4chCDhc=
Received: from BYAPR11MB2792.namprd11.prod.outlook.com (52.135.225.142) by BYAPR11MB2997.namprd11.prod.outlook.com (20.177.226.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.24; Wed, 30 Oct 2019 21:12:57 +0000
Received: from BYAPR11MB2792.namprd11.prod.outlook.com ([fe80::2950:14d4:f3c2:851a]) by BYAPR11MB2792.namprd11.prod.outlook.com ([fe80::2950:14d4:f3c2:851a%6]) with mapi id 15.20.2387.028; Wed, 30 Oct 2019 21:12:57 +0000
From: "Ramesh Sivakolundu (sramesh)" <sramesh@cisco.com>
To: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>, "opsawg@ietf.org" <opsawg@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>
Thread-Topic: [ippm] FW: New Version Notification for draft-brockners-opsawg-ioam-deployment-00.txt
Thread-Index: AQHVj2bNJ/+uo4JdwUGtYsuPszr7OA==
Date: Wed, 30 Oct 2019 21:12:56 +0000
Message-ID: <1C00B904-EE3D-487E-BAE7-D0C0BD14D1AA@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=sramesh@cisco.com;
x-originating-ip: [128.107.241.181]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 16b13af7-89d1-415c-b1af-08d75d7defc4
x-ms-traffictypediagnostic: BYAPR11MB2997:
x-ms-exchange-purlcount: 5
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <BYAPR11MB299717DA73B8CA384BDAFA07B3600@BYAPR11MB2997.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 02065A9E77
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(366004)(39860400002)(376002)(346002)(136003)(13464003)(199004)(189003)(66574012)(6436002)(6506007)(476003)(99286004)(71200400001)(7736002)(71190400001)(305945005)(15650500001)(25786009)(316002)(486006)(6512007)(2906002)(6486002)(229853002)(6306002)(450100002)(8936002)(36756003)(66066001)(110136005)(66476007)(14454004)(8676002)(66446008)(26005)(66556008)(64756008)(76116006)(33656002)(66946007)(81166006)(81156014)(4001150100001)(2616005)(5660300002)(186003)(86362001)(2201001)(6116002)(478600001)(2501003)(966005)(14444005)(53546011)(256004)(6246003)(102836004)(3846002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2997; H:BYAPR11MB2792.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: dSJoXMSwGdQ6ngoC+xqa8e92kDBvlCn/Es9SQhKLamcd6tmAP3zRP7vdcBOkaYymGtgKfM3E342I29Se8njpkHluBt0/29V+01LkwLqlqeGQ542mRMHIFk4hMKQY7kj23M8mpZ3ngYi/efB5L20caohOMY7H2b9GWqwR7rRvhq+3mvszTq7oskr1H/q+oPD7R/vDQqTLj+LodsClTq4Bgu1jfBw6P3ZBALNfNE3P7oBJ5N5XddOmUDhwMPi2REqpbaAYhod9DEy6gmgyXPxkgou8LMU9RUTK0zLisvRWP+u21f0Uf2914XxcbVyZPxEUv2dD6RxfosDbcj5dvEbSKz8WV1a2q4TbQnHZvCnqW4RAEgolelUxSpCE1a67Egyyat2jv1JFrd56UyFm+xnLvxVd/o2SG9n4njrRFN5eyS2xfCUPsFpPErBQ3Owk/qYaR6wI2OVhd31Uv1EdEiXzmV1DOPn8ik5BRTwBfT8NCUI=
Content-Type: text/plain; charset="utf-8"
Content-ID: <772CB66EDC159742BA8B3AB9387E03E9@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 16b13af7-89d1-415c-b1af-08d75d7defc4
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Oct 2019 21:12:57.0135 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 5vWg8X6F+100tZBNZ6R59JrIOXcKP9Wg8uBybzDVBkvKrenQMt77rILdGMYKBJ/y9Nt0njuig36EQUgO5M/xmQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2997
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.25, xch-aln-015.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/RX6zlJp2PxFtXRBXjx1lLGZfaqE>
Subject: Re: [ippm] FW: New Version Notification for draft-brockners-opsawg-ioam-deployment-00.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2019 21:13:02 -0000

Can we include IPv4 /w GRE header in Section 5.3  "GRE"?

Few edits:

5.3.  GRE

   IOAM encapsulation for NSH is defined in [I-D.weis-ippm-ioam-eth].

Typo, instead of NSH it should be GRE.

Regards,

-Ramesh

On 10/30/19, 9:23 AM, "ippm on behalf of Frank Brockners (fbrockne)" <ippm-bounces@ietf.org on behalf of fbrockne@cisco.com> wrote:

    
    Several of you have indicated multiple times that it would really help, if we had an "IOAM deployment" draft that discusses the various deployment considerations for IOAM all in one place - and serves as a single entry point for IOAM, referencing in the different IOAM related drafts.
    
    We finally arrived at creating an initial revision - and we greatly appreciate your thoughts and comments how to evolve this further.
    
    Thanks much, Frank
    
    
    > -----Original Message-----
    > From: internet-drafts@ietf.org <internet-drafts@ietf.org>
    > Sent: Mittwoch, 30. Oktober 2019 17:17
    > To: Daniel Bernier <daniel.bernier@bell.ca>; Frank Brockners (fbrockne)
    > <fbrockne@cisco.com>; daniel.bernier@bell.ca <daniel.bernier@bell.ca>;
    > Shwetha Bhandari (shwethab) <shwethab@cisco.com>
    > Subject: New Version Notification for draft-brockners-opsawg-ioam-
    > deployment-00.txt
    > 
    > 
    > A new version of I-D, draft-brockners-opsawg-ioam-deployment-00.txt
    > has been successfully submitted by Frank Brockners and posted to the IETF
    > repository.
    > 
    > Name:		draft-brockners-opsawg-ioam-deployment
    > Revision:	00
    > Title:		In-situ OAM Deployment
    > Document date:	2019-10-30
    > Group:		Individual Submission
    > Pages:		22
    > URL:            https://www.ietf.org/internet-drafts/draft-brockners-opsawg-ioam-
    > deployment-00.txt
    > Status:         https://datatracker.ietf.org/doc/draft-brockners-opsawg-ioam-
    > deployment/
    > Htmlized:       https://tools.ietf.org/html/draft-brockners-opsawg-ioam-
    > deployment-00
    > Htmlized:       https://datatracker.ietf.org/doc/html/draft-brockners-opsawg-
    > ioam-deployment
    > 
    > 
    > Abstract:
    >    In-situ Operations, Administration, and Maintenance (IOAM) records
    >    operational and telemetry information in the packet while the packet
    >    traverses a path between two points in the network.  This document
    >    provides a framework for IOAM deployment and provides best current
    >    practices.
    > 
    > 
    > 
    > 
    > 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.
    > 
    > The IETF Secretariat
    
    _______________________________________________
    ippm mailing list
    ippm@ietf.org
    https://www.ietf.org/mailman/listinfo/ippm