Re: [Raw] Call for adoption of draft-theoleyre-raw-oam-support-01

Janos Farkas <Janos.Farkas@ericsson.com> Thu, 02 April 2020 14:47 UTC

Return-Path: <Janos.Farkas@ericsson.com>
X-Original-To: raw@ietfa.amsl.com
Delivered-To: raw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C44C3A13C2 for <raw@ietfa.amsl.com>; Thu, 2 Apr 2020 07:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 wlZi1ic38t9f for <raw@ietfa.amsl.com>; Thu, 2 Apr 2020 07:47:06 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-eopbgr140081.outbound.protection.outlook.com [40.107.14.81]) (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 D83663A13C6 for <raw@ietf.org>; Thu, 2 Apr 2020 07:47:05 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dM7M/azASKBvRP4mcfBagasu7ddIzhLaCRcW6gu7Jw7J9OJ75pm6bLbmj9NQghawpQskgxzztPf8XLdZzE9QLtwt/d/wf+qsZppGG7SqrX+OQ/+3cAJ6GEUOwrA3xHQ7oeeVTpompe2g/8GWbR5dtcBdbBSMfzJaI6k+fwHDJEB+Q0raAvA5JHXzMuKmWB6MpmsypGyYpSFEK18f+WLEySig/2JoENrrDcWGkBrIpGTC3kR1fsnZqRyYURxE/dMZj8NhILUE1OsLyRuHs7QcCDckkQOjC/5GAlkpjzpTAeYlNgTHUfYnT8/M4NKRt3S7tPUqZaQDn3mU26M7w8ydXQ==
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=Ithfuch1DRNTMQf48PMx7uPWLQWBpi296JHvd3aoX9U=; b=coAwcMlkozNzhGjmEQLHvajGDQQiybpJA32CbQUZB1b1vrsmK2w5ZEqTKTUh+/QC4t4zpBNeyG2CXO2CpWeKJ+EEMTlCLcwLw+wpYiXT6w9e6cTkvNEqLHSX+rau4y0Q2rF5G/Q6y3QfhX54Zo98DxBlx3tGN10E1sBZ7SpB3o92haFDd4kXVV0sruDoyPiUj2/BnH05gOF9dzv6pRox+iJLW/NjTEnUPiht6s7v1fYZTJwtdwGy5+pBHWhwxxlc0fI3023FYmgy8QzfApnjZ6irAzpLaakMNG99are25UaSwVXW2H3PZqHDeHZjl0hP/DNacMIl5FYS6ekS3lJigA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Ithfuch1DRNTMQf48PMx7uPWLQWBpi296JHvd3aoX9U=; b=LIQd4Y9M5OuUOX6eBTl5vA/TZv5bKn+1MzeiyH4YMTkqaq8ExbPLB/wpIlYDc7ahY1u6IA2eokeUl+pL4PRzWEmsjttJPawS7mX1nMRA2nxAv5en6p0w7+jZoHmShEACJPDgBLsWanpP+p2CRGdZ0XLdBklGeZbCOkaGDu5cSI8=
Received: from VI1PR07MB4415.eurprd07.prod.outlook.com (20.176.2.145) by VI1PR07MB4256.eurprd07.prod.outlook.com (20.176.2.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.9; Thu, 2 Apr 2020 14:47:03 +0000
Received: from VI1PR07MB4415.eurprd07.prod.outlook.com ([fe80::e02a:72a3:7222:f505]) by VI1PR07MB4415.eurprd07.prod.outlook.com ([fe80::e02a:72a3:7222:f505%2]) with mapi id 15.20.2878.014; Thu, 2 Apr 2020 14:47:03 +0000
From: Janos Farkas <Janos.Farkas@ericsson.com>
To: Fabrice Theoleyre <theoleyre@unistra.fr>
CC: "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>, "raw@ietf.org" <raw@ietf.org>, Rick Taylor <rick@tropicalstormsoftware.com>
Thread-Topic: [Raw] Call for adoption of draft-theoleyre-raw-oam-support-01
Thread-Index: AdYGe8mxEVBupFh/T4SqJGrVNRXqOgBKEQsQABf2UoAAAJY4MAAXiphAACU++YAAAPGHAA==
Date: Thu, 02 Apr 2020 14:47:03 +0000
Message-ID: <VI1PR07MB4415AEFCC0FE0D19288072C0F2C60@VI1PR07MB4415.eurprd07.prod.outlook.com>
References: <38A5475DE83986499AEACD2CFAFC3F9801F5831EA3@tss-server1.home.tropicalstormsoftware.com> <VI1PR07MB4415D97AA23303477DD35362F2C80@VI1PR07MB4415.eurprd07.prod.outlook.com> <9A3665D9-A268-4337-9ABB-73B58BE3AFE8@unistra.fr> <MN2PR11MB3565D86C7D6E24274B63F154D8C90@MN2PR11MB3565.namprd11.prod.outlook.com> <VI1PR07MB441545ED3D39E8F9683B4D48F2C90@VI1PR07MB4415.eurprd07.prod.outlook.com> <F6078936-76D9-4C81-8AEE-164D77D4BE0B@unistra.fr>
In-Reply-To: <F6078936-76D9-4C81-8AEE-164D77D4BE0B@unistra.fr>
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=Janos.Farkas@ericsson.com;
x-originating-ip: [176.63.28.146]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: fd4cc63a-2b6b-4190-5fac-08d7d714b50f
x-ms-traffictypediagnostic: VI1PR07MB4256:
x-microsoft-antispam-prvs: <VI1PR07MB4256016E20E4F2DEA374AFC1F2C60@VI1PR07MB4256.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0361212EA8
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR07MB4415.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(4636009)(39860400002)(366004)(136003)(346002)(396003)(376002)(81156014)(8676002)(81166006)(6916009)(7696005)(186003)(71200400001)(26005)(478600001)(54906003)(316002)(2906002)(52536014)(5660300002)(53546011)(8936002)(966005)(6506007)(76116006)(66946007)(66476007)(66556008)(64756008)(66446008)(4326008)(9686003)(86362001)(66574012)(33656002)(55016002); DIR:OUT; SFP:1101;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: mBcN9CobO4GjXmsRoSEHh3BEddKHKuqbFAuIWpd6NLikuTvWrTs7E9JWgCMzFPGHSKnHcmsPl4zkz4SZv0/RUU5Bp6p8wJtArIJnuxGbi5IycjdIV29I0WDm81yFiu7S9I0/OUtydqgDXoQnRwXJ1QYFe4FoFfZaRLN0Xstql0ajTAr8T56XInE1D75l9YGg1kokjdwH4BsTZnJikhOB0PyjCsLWsxQNpm8dkdA+3HytHAX2/aU40IxAiZ64dfbrO4L4FOyo8QSeeGeVL+idGviqkHHr8MTrjIRl5USrJ5cfg+a8zmv/DFEbgXFmdmPT6qswrHVN/1CnruO7xE1y9PIr/QxUK+KSQjr0NihYQU5XUToj7245QQNAOlqrXWl0IpmdRIJGJISDiQ5918x3v3d/a10AOMVaoBAVaNXrW2GBaSz4lWy+42c0WfcDF6xYRanovmkWOq8KXN3F8tuqBqrQ/YJWe9o7RzWj9VhkVg4uh05F9tOQdIt5ECdscSqStNTKFib4fLSBEGIieTLuTA==
x-ms-exchange-antispam-messagedata: iGilMhA3VCY8bYK8Znx+BvJS+fOp5q4RwY487XYpQwQtpW2emjWpH0gQQEnhMMt54QE/M8W+X1A07NUHbDLraGS28HuOO7Os1su9zgnWvmDjQk5ctbzkMy6/u+Qz7VWeUVfbf65mC+T5z2fldqhyug==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_VI1PR07MB4415AEFCC0FE0D19288072C0F2C60VI1PR07MB4415eurp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: fd4cc63a-2b6b-4190-5fac-08d7d714b50f
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Apr 2020 14:47:03.2156 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: SZh8okcB9ZXw2H46j2wFRv/5iqyUZQ8JRW5rAI/fjsTlLoTBzG5pdhZVuT3yooP1jQUkisA0ttVFNySuZyT7gbR0MvqjANSsfkJubl3mJm4=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4256
Archived-At: <https://mailarchive.ietf.org/arch/msg/raw/FqOc7c13CAMv93kCoIbgGpMwixs>
Subject: Re: [Raw] Call for adoption of draft-theoleyre-raw-oam-support-01
X-BeenThere: raw@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: reliable and available wireless <raw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/raw>, <mailto:raw-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/raw/>
List-Post: <mailto:raw@ietf.org>
List-Help: <mailto:raw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/raw>, <mailto:raw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2020 14:47:09 -0000

Dear Fabrice,

My point is that we have “Requirements Document” in the charter. I haven’t seen draft for it yet.
Having an OAM requirements section int the Requirements Document is not less readable or referenceable than a separate draft. Actually, there is gain of saving separate intro, security considerations and so on.

Best regards,
Janos


From: Fabrice Theoleyre <theoleyre@unistra.fr>
Sent: Thursday, April 2, 2020 4:17 PM
To: Janos Farkas <Janos.Farkas@ericsson.com>
Cc: Pascal Thubert (pthubert) <pthubert=40cisco.com@dmarc.ietf.org>; raw@ietf.org; Rick Taylor <rick@tropicalstormsoftware.com>
Subject: Re: [Raw] Call for adoption of draft-theoleyre-raw-oam-support-01

Dear Janos,

I guess that focusing on the OAM requirements for RAW and more importantly on what makes it so specific is of interest.

Merging OAM and general requirements in a single document may be an option, but I’m afraid of having something very big, and complicated to digest by everybody.

Pedagogically, shouldn’t we split both documents?
What overlapping parts do you envision between both of them?

Best regards,
Fabrice




Le 1 avr. 2020 à 22:40, Janos Farkas <Janos.Farkas@ericsson.com<mailto:Janos.Farkas@ericsson.com>> a écrit :

Dear Fabrice and Pascal,

Perhaps, I have not elaborated my points too much.

I of course also see a lot of value in collecting the OAM requirements for RAW. It is just not obvious to me that this draft is a collection of RAW OAM requirements. For instance, the title is not "OAM Requirements" or alike.

A requirements document is listed among the RAW milestones.
OAM requirements, clearly phrased as OAM requirements, could be part of the RAW requirements document.
I understand this is an early draft. Given the comments, maybe updated text could be good input to RAW requirements document.

Best regards,
Janos


-----Original Message-----
From: Pascal Thubert (pthubert) <pthubert=40cisco.com@dmarc.ietf.org<mailto:pthubert=40cisco.com@dmarc.ietf.org>>
Sent: Wednesday, April 1, 2020 11:25 AM
To: Fabrice Theoleyre <theoleyre@unistra.fr<mailto:theoleyre@unistra.fr>>; Janos Farkas <Janos.Farkas@ericsson.com<mailto:Janos.Farkas@ericsson.com>>
Cc: raw@ietf.org<mailto:raw@ietf.org>; Rick Taylor <rick@tropicalstormsoftware.com<mailto:rick@tropicalstormsoftware.com>>
Subject: RE: [Raw] Call for adoption of draft-theoleyre-raw-oam-support-01

Dear all

The intended status of the draft is Standards Track. It includes
conformance
language, e.g.,:

" The ping packets must be labeled in the same way as the data
packets of
the flow to monitor."

" These metrics should be collected:”

Yes, this is something we have to address.

Well that language can be found in informational as well; if it must it must, fact of life that can be observed and described in an informational. Publishing as informational for all I know does not preclude such language. Note that this is not using BCP 14.





To me, the draft seems to be solution, hence, outside of the current
RAW
charter.

Actually, we have tried to explain the challenges created by
implementing OAM with RAW networks. We tried to not detail a given
solution. While we point to existing works for each of ”challenge”, we
don’t recommend a specific one.

Anyway, maintaining an informational status was our objective. If the
draft is too ”solution oriented” in some parts, this is probably
something we can address.
Let us know the incriminated parts.

God for me then...
I'm happy that RAW works on this draft for now to ensure that the RAW angle is described in full.
It is up to the chairs and ADs to transfer or kindly ask for reviews from DetNet at any stage if that can help.

Be safe!

Pascal





Thinking then on:
1) Is the RAW working group the correct WG for this work?
Also in the RAW charter:
" RAW extends the DetNet Working Group concepts"
As I understand, RAW OAM should be an extension of DetNet OAM, not
RAW
OAM on its own. The draft does not mention or refer to DetNet OAM.
Well, DetNet OAM has not been finished yet, but there are drafts for it:

https://datatracker.ietf.org/doc/draft-ietf-detnet-mpls-oam/
https://datatracker.ietf.org/doc/draft-mirsky-detnet-ip-oam/
Perhaps the OAM work could be done in the DetNet WG. DetNet OAM
could
be extended for wireless in the DetNet WG.



So, I do not support the adoption of this draft.

Regards,
Janos


-----Original Message-----
From: RAW <raw-bounces@ietf.org<mailto:raw-bounces@ietf.org>> On Behalf Of Rick Taylor
Sent: Monday, March 30, 2020 12:14 PM
To: raw@ietf.org<mailto:raw@ietf.org>
Subject: [Raw] Call for adoption of
draft-theoleyre-raw-oam-support-01

Hi All,

The authors of: draft-theoleyre-raw-oam-support-01 (have asked for a
call
for working group adoption of their draft.


The link to the draft is:
https://datatracker.ietf.org/doc/draft-theoleyre-raw-
oam-support/


This is your opportunity to express your opinion.

A decision will be made on/after 13th April.

Cheers,

Rick and Eve
Co-chairs

--
RAW mailing list
RAW@ietf.org<mailto:RAW@ietf.org>
https://www.ietf.org/mailman/listinfo/raw

--
RAW mailing list
RAW@ietf.org<mailto:RAW@ietf.org>
https://www.ietf.org/mailman/listinfo/raw

--
RAW mailing list
RAW@ietf.org<mailto:RAW@ietf.org>
https://www.ietf.org/mailman/listinfo/raw