IETF Logo Mail Archive

Re: [Ioam] [EXT] Re: Updated IOAM Proposed Charter

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 14 February 2017 15:54 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: ioam@ietfa.amsl.com
Delivered-To: ioam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 487251294F8 for <ioam@ietfa.amsl.com>; Tue, 14 Feb 2017 07:54:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 N9pdXH19GXrf for <ioam@ietfa.amsl.com>; Tue, 14 Feb 2017 07:54:12 -0800 (PST)
Received: from mxa2.tigertech.net (mxa2.tigertech.net [208.80.4.162]) (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 D68BD129453 for <ioam@ietf.org>; Tue, 14 Feb 2017 07:54:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id BE5BD247368; Tue, 14 Feb 2017 07:54:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1487087652; bh=ZrA7ofhXp7DbDsUnzFo6Dh17JAEw1g0yNVWRyeX1AN0=; h=Subject:To:References:From:Date:In-Reply-To:From; b=Q8+TPuI4tx3MBGiC4RXQabrBbhmZny4FSo/K7GWwgpKrdezTuWVVrmP23r3Iojjxo 2DHYlcRRosKyMPYHNJEQkDWtQVjvdN2z7axymlvOSIDEUZpDCnjFvHRqDpPBgGBPdw 2Wgpd+q+EvjKx9M2sthWET1GwQEESdKO5VamRKrI=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 55A073A070C; Tue, 14 Feb 2017 07:54:12 -0800 (PST)
To: Tal Mizrahi <talmi@marvell.com>, "ioam@ietf.org" <ioam@ietf.org>
References: <adeb1814acd74ebaafe10d4a5086ba0f@IL-EXCH01.marvell.com> <369755ec-7cb5-0127-3ac4-e97b1a2d1810@joelhalpern.com> <ca23921a51054c0eba31160818197c8e@IL-EXCH01.marvell.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <0aaa5af4-bdbd-289c-db78-c68d3ad5c48d@joelhalpern.com>
Date: Tue, 14 Feb 2017 10:54:11 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <ca23921a51054c0eba31160818197c8e@IL-EXCH01.marvell.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ioam/IFcSPBaSc4CneEFCYfxExJbjWjM>
Subject: Re: [Ioam] [EXT] Re: Updated IOAM Proposed Charter
X-BeenThere: ioam@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion on In-Situ OAM <ioam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ioam>, <mailto:ioam-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ioam/>
List-Post: <mailto:ioam@ietf.org>
List-Help: <mailto:ioam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ioam>, <mailto:ioam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 15:54:14 -0000

Making the challenges a separate bullet would help.  I might refer to 
challenges and constraints rather than just challenges.

Yours,
Joel

On 2/14/17 8:22 AM, Tal Mizrahi wrote:
> Hi Joel,
>
> Point well taken. I would suggest to split the following paragraph into two paragraphs, one discussing the scope/domain, and the other discussing the "various challenges". Please let us know if that addresses your concern.
>
> *  Scope of in-situ OAM operation. In-Situ OAM operations are defined for a
> specific operational domain. In-situ OAM data-records are added and removed at
> domain boundaries and updated by nodes within the in-situ OAM domain. Procedure
> to deal with various challenges in packet forwarding and error handling such as
> ECMP processing, path MTU and ICMP message handling when in-situ OAM is enabled
> in an in-situ OAM domain.
>
> Thanks,
> Tal.
>
>
>
>
>> -----Original Message-----
>> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
>> Sent: Monday, February 13, 2017 5:52 PM
>> To: Tal Mizrahi; ioam@ietf.org
>> Subject: [EXT] Re: [Ioam] Updated IOAM Proposed Charter
>>
>> External Email
>>
>> ----------------------------------------------------------------------
>> Maybe I am missing something, but it seems to me that issues such as ECMP and
>> path MTU are not "domain" or "scope" specific.  That is why I had asked that
>> reference to these issues be put into the lead paragraph.
>>
>> Yours,
>> Joel
>>
>> On 2/13/17 9:48 AM, Tal Mizrahi wrote:
>>> Hi,
>>>
>>>
>>>
>>> The charter draft has been updated based on the comments received on
>>> the last few days:
>>>
>>> https://datatracker.ietf.org/doc/charter-ietf-ioam/
>>>
>>>
>>>
>>> The main changes compared to the previous draft:
>>>
>>> -          A few terminology and phrasing changes based on comments
>>> received on the list.
>>>
>>> -          New text regarding the encapsulations that the working group
>>> will initially focus on.
>>>
>>> -          Updated the text about consultation with other working groups.
>>>
>>> -          New text about cooperation with other standard bodies.
>>>
>>>
>>>
>>> Comments will be welcome.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Tal.
>>>
>>>
>>>
>>> _______________________________________________
>>> Ioam mailing list
>>> Ioam@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ioam
>>>

v2.23.0 | Report a Bug | By Email