Re: [spring] Ben Campbell's No Objection on draft-ietf-spring-oam-usecase-09: (with COMMENT)

<Ruediger.Geib@telekom.de> Thu, 14 December 2017 09:56 UTC

Return-Path: <Ruediger.Geib@telekom.de>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC562124BE8; Thu, 14 Dec 2017 01:56:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.319
X-Spam-Level:
X-Spam-Status: No, score=-4.319 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_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de header.b=uQkYhd6d; dkim=pass (1024-bit key) header.d=telekom.onmicrosoft.de header.b=JnryWCfW
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 KKcdfB_YwUJe; Thu, 14 Dec 2017 01:56:42 -0800 (PST)
Received: from MAILOUT21.telekom.de (MAILOUT21.telekom.de [80.149.113.251]) (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 96E89127876; Thu, 14 Dec 2017 01:56:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1513245402; x=1544781402; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=59iCj4yikWb9L/ys9OLblEW4LU+N8J46Q6H8klIIPKI=; b=uQkYhd6d0uIaIFCqHG+1nyOlz6prx5MHIJvNG7EsPM4lGuZEMXd6R7Yp aI4TeptwnB3Ad79O6e0Vph6s8TnHlebaw/m0GbMU0pCwYtbmHrkJrGxDo Dvo3EmxCBuMyOSPLCfLAxq01FxXd11uAGTQ3HFt2FnJECp2cxgUBO3j3u Kpo60t5wp+7PjqFqX1ScoxMIgppGxrQl0mGRJMoNVzf156myde2pR4Fhk zZxJRv1k2EqEBQpeQqToYuyk4N75IkWPsurlbFNF2pWVqsZacjk53nnPm vYdv8c9lljW3mC/7VM5iPG0SZoYArusW025mmMuQ5U1R/ztNPOgixe/Eo Q==;
Received: from q4de8psa04t.blf.telekom.de ([10.151.13.130]) by MAILOUT21.telekom.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Dec 2017 10:56:30 +0100
X-IronPort-AV: E=Sophos;i="5.45,400,1508796000"; d="scan'208";a="779207087"
Received: from he101951.emea1.cds.t-internal.com ([10.169.118.77]) by Q4DE8PSA04V.blf.telekom.de with ESMTP/TLS/AES256-SHA; 14 Dec 2017 10:56:30 +0100
Received: from HE105825.EMEA1.cds.t-internal.com (10.169.118.47) by HE101951.emea1.cds.t-internal.com (10.169.118.77) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Thu, 14 Dec 2017 10:56:29 +0100
Received: from HE106564.emea1.cds.t-internal.com (10.171.40.16) by HE105825.EMEA1.cds.t-internal.com (10.169.118.47) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Thu, 14 Dec 2017 10:56:29 +0100
Received: from GER01-FRA-obe.outbound.protection.outlook.de (51.4.80.22) by O365mail01.telekom.de (172.30.0.234) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Thu, 14 Dec 2017 10:56:16 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.onmicrosoft.de; s=selector1-telekom-onmicrosoft-de; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=59iCj4yikWb9L/ys9OLblEW4LU+N8J46Q6H8klIIPKI=; b=JnryWCfWY7ZgFiwY0bEFmiO2HdfuRk45h7ARFquARrrFxcSAwrbtbC2GmjuM9uwogo+CpSBpui5i/LG+pE92dQyBaAT79XyuvvArqZToerQxZKAxIa6uM7nBOUo28YDMElsL8pSYHQzAVcVPwOhi8Qcd7U0WgGp6utvGqOSREBs=
Received: from LEXPR01MB0094.DEUPRD01.PROD.OUTLOOK.DE (10.158.163.139) by LEXPR01MB0093.DEUPRD01.PROD.OUTLOOK.DE (10.158.163.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.302.9; Thu, 14 Dec 2017 09:56:28 +0000
Received: from LEXPR01MB0094.DEUPRD01.PROD.OUTLOOK.DE ([fe80::bd79:9e12:5cb0:ec5a]) by LEXPR01MB0094.DEUPRD01.PROD.OUTLOOK.DE ([fe80::bd79:9e12:5cb0:ec5a%14]) with mapi id 15.20.0302.014; Thu, 14 Dec 2017 09:56:28 +0000
From: Ruediger.Geib@telekom.de
To: ben@nostrum.com
CC: draft-ietf-spring-oam-usecase@ietf.org, aretana.ietf@gmail.com, spring-chairs@ietf.org, bruno.decraene@orange.com, spring@ietf.org, iesg@ietf.org
Thread-Topic: Ben Campbell's No Objection on draft-ietf-spring-oam-usecase-09: (with COMMENT)
Thread-Index: AQHTdI4AfmP+sZBYwkWn0bm6cJYEAqNCliDA
Date: Thu, 14 Dec 2017 09:56:28 +0000
Message-ID: <LEXPR01MB00946628BEF7BAD831A50A659C0A0@LEXPR01MB0094.DEUPRD01.PROD.OUTLOOK.DE>
References: <151322313115.6120.8756591218425505436.idtracker@ietfa.amsl.com>
In-Reply-To: <151322313115.6120.8756591218425505436.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Ruediger.Geib@telekom.de;
x-originating-ip: [164.19.3.100]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; LEXPR01MB0093; 6:xWZ5AlR+Ing0jhNseV2bzK1bK++6NL+rHgvkRI6MzGfLSfQRJxCGgXvnkacIQEuN1wcyYzmYaPn1sTtoDJ4nfKLcbSKmqAPv4dY4JC/4Wuvg2mDqW4THq1c1EAud/vlHZu9peIcJv5JF8TMThXufc/dAa8UeoCZ3aVkFkO/qM5iL9KUQoU42leXzPb77hjwOhnTz38Fl9HYrbyDBNkXG8kQMGSvYVDX1fq+QIiBE8WJo0Wxj/6qe8NJyGKm17hzbtldKHGC7znImuVA82xtZ0hLRNzoCS/cfi6kpF5tkfnWQyupY8lArJ0Pag7dOEQRA2q5CKBE15yHWoaItX5Rd7pWy11WG18+tkFtW3B3weiE=; 5:2RfXf8lFDtF1jUnaa3/68r6s8C47N3ktDDdiR5Tfw+l9KYrZhIsz1Xkl1qtYAyG0n4VRV8V/jD4kDg3n9n8vNS+G4yViRRYSEBynkbdoLTo8PKFgl5GhrqF3XCP7P5A/c9Nj26KurSKLtzF/LX6HDxIpTdIluE8Hi52oAs875eY=; 24:DdWEhf6CDOWrSSqFJFqWhuoAZS/yWAVJ8sexEVaQ642r0Ixfj8Md86fNI+MM0AEGUpP09YfvjycMxGm7ImSid02GHL21wNJT3DPIMcpOspY=; 7:OIoVO7BRxFp1BkL5qMwVXY/QL6+hZHo6nuqTqs4RSGUlvj72Ezl9c0UjRluX70UvBmOfSbqu4zf8Cbuv7HurhKwu1WIdj2QXUNwRNsxU3zwa4rRvBsv3qTZDGAQ6zUhj7CyrL5ydNlK9QoSxEmrJrMx2al4KibDixMD3002E68fnEHdkEf35VhgOdCIuUQVoCE+0oIxmokcZRJN6rodQJAHvZ1akHyYyJUQCJlk22LpbR/l5MuV4crgLR+rNFe6Q
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: b4442828-2695-4cf5-cfdc-08d542d8f228
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(5600026)(4604075)(2017052603307); SRVR:LEXPR01MB0093;
x-ms-traffictypediagnostic: LEXPR01MB0093:
x-microsoft-antispam-prvs: <LEXPR01MB00939390D96884630B1078869C0A0@LEXPR01MB0093.DEUPRD01.PROD.OUTLOOK.DE>
x-exchange-antispam-report-test: UriScan:(120809045254105)(192374486261705)(18271650672692);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(3231023)(10201501046)(6041248)(20161123555025)(20161123564025)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123558100)(6072148)(201708071742011); SRVR:LEXPR01MB0093; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:LEXPR01MB0093;
x-forefront-prvs: 05214FD68E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(396003)(366004)(346002)(376002)(189003)(199004)(81156014)(561944003)(230783001)(97736004)(8936002)(55016002)(33656002)(81166006)(7696005)(105586002)(8676002)(2900100001)(75402003)(305945005)(85202003)(66066001)(6116002)(86362001)(478600001)(14454004)(52396003)(106356001)(3846002)(7736002)(102836003)(2950100002)(72206003)(6916009)(966005)(53936002)(6306002)(68736007)(4326008)(5660300001)(3280700002)(3660700001)(316002)(5250100002)(76176011)(74482002)(54906003)(59450400001)(39060400002)(85182001)(9686003)(2906002)(777600001); DIR:OUT; SFP:1101; SCL:1; SRVR:LEXPR01MB0093; H:LEXPR01MB0094.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b4442828-2695-4cf5-cfdc-08d542d8f228
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Dec 2017 09:56:28.5298 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LEXPR01MB0093
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/er1JGsrhabeXY2H9b9ISuY4gG9A>
Subject: Re: [spring] Ben Campbell's No Objection on draft-ietf-spring-oam-usecase-09: (with COMMENT)
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 09:56:45 -0000

Hi Ben,

thanks for your comments. I started to agree text changes with my co-editor. Takeshi and you commented on the same sentence, which can't be parsed. 

   Your comment: -10 --5th paragraph: I can't parse the last sentence.
   Takeshi's comment: 3. This sentence "As it is necessary to know that the information is
      stale is order to follow the instruction, as is the case with for
      example convergence events that may be ongoing at the time of
      diagnostic measurement." is not easy to understand for me. I see some typo
      in this sentence as well.

This text proposal has been agreed between Carlos and me:

OLD: As it is necessary to know that the information is
   stale is order to follow the instruction, as is the case with for
   example convergence events that may be ongoing at the time of
   diagnostic measurement.

NEW: To carry out a desired measurement properly, the PMS must be aware of and respect the actual route changes, convergence events, as well as the assignment of Segment IDs relevant for measurements. At a minimum, the PMS must be able to listen to IGP topology changes, or pull routing and segment information from routers signaling topology changes.

Regards,

Ruediger

-----Ursprüngliche Nachricht-----
Von: Ben Campbell [mailto:ben@nostrum.com] 
Gesendet: Donnerstag, 14. Dezember 2017 04:46
An: The IESG <iesg@ietf.org>
Cc: draft-ietf-spring-oam-usecase@ietf.org; aretana.ietf@gmail.com; spring-chairs@ietf.org; bruno.decraene@orange.com; spring@ietf.org
Betreff: Ben Campbell's No Objection on draft-ietf-spring-oam-usecase-09: (with COMMENT)

Ben Campbell has entered the following ballot position for
draft-ietf-spring-oam-usecase-09: No Objection

When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-spring-oam-usecase/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Substantive Comments:

- General: I note there has been discussion about why this draft is Informational rather than something else. There's an explanation in the shepherd's writeup. It would be helpful to have the same explanation as a note in the draft. (People rarely read the shepherd's report once an RFC is
published.)

- 3, last paragraph: " Further options, like deployment of a PMS connecting to the MPLS domain by a tunnel only require more thought, as this implies security aspects." I have trouble parsing that. Is it intended as an open issue, or a statement that the "further options" are out of scope? Also, consider deleting the word "only".

-4.1, 2nd to last paragraph:
I'm not sure what to make of the "In theory at least," prefix. Normally IETF RFCs are about what (we hope) works in _practice_.

-10, last paragraph: I don't understand the intent of this paragraph.

Editorial Comments and Nits:
- section1, first sentence: s/operator/operators
- same section, first bullet: "operators" is repeated twice. (i.e. "operators
operators") -- third bullet: "allows to transport" should be either "allows <something> to transport" or "allows the transport". -- 4th bullet, last
sentence: I suggest the following: OLD: [...] since both sender and receiver have the same clock, sequence numbers to ease the measurement...). NEW: [...] since both sender and receiver have the same clock and sequence numbers to ease the measurement.).

-10, 2nd paragraph: " The PMS allows to insert "
That should either be "allows <something> to insert" or "Allows the insertion"
-- 3rd paragraph: I can't parse the sentence. Should "avoid a PMS to insert traffic" be "prevent a PMS from inserting traffic"? -- 4th paragraph:
s/personal/personnel -- 5th paragraph: I can't parse the last sentence. -- 6th
paragraph: "As soon as the PMS has an indication, that its IGP or MPLS topology are stale..." The comma between "indication" and "that" should be removed.