[Bier] draft-ietf-bier-oam-requirements-00: PMTUD requirement in BIER OAM Requirements

"eckert@cisco.com" <eckert@cisco.com> Fri, 06 November 2015 04:28 UTC

Return-Path: <eckert@cisco.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5D701B34E3 for <bier@ietfa.amsl.com>; Thu, 5 Nov 2015 20:28:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 rn_K8DxpgVH9 for <bier@ietfa.amsl.com>; Thu, 5 Nov 2015 20:28:56 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5042B1B34E2 for <bier@ietf.org>; Thu, 5 Nov 2015 20:28:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1543; q=dns/txt; s=iport; t=1446784136; x=1447993736; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=6XO4b0dc9keVJnJiAHGCKcdoUQh7C3N1JRe4/wzyOLk=; b=ePhSk6/JBjMq49Q3eQdyt0SZvIlom+A9qoVyqfSIk2wTmco6jrZxPlrR 9L9z8G5/xXnphUlb29ibXDBrj0M57FVN+QPApevIfh/82j3NSdWs+aLR6 t/j/r1JdvTy0temma5JyBy2cxaqcdU1MHOfkHc2pBjRS5djqfvkEq9Ayj k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AOAgCEKzxW/4sNJK1egztTvGKCGgENgWAhhW8CgUA4FAEBAQEBAQGBCoQ2AQEEOj8QIwklDwVJiEENwQgBAQEBAQEBAQEBAQEBAQEBAQEBAQEUBIVZjh2BFQWOEYg3AYUch34IgVqWdoNyHwEBQoQlHYVIAQEB
X-IronPort-AV: E=Sophos;i="5.20,250,1444694400"; d="scan'208";a="205466133"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-6.cisco.com with ESMTP; 06 Nov 2015 04:28:55 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id tA64StVo012026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Nov 2015 04:28:55 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id tA64SsLI028252; Thu, 5 Nov 2015 20:28:54 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id tA64SssL028251; Thu, 5 Nov 2015 20:28:54 -0800
Date: Thu, 05 Nov 2015 20:28:54 -0800
From: "eckert@cisco.com" <eckert@cisco.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>
Message-ID: <20151106042854.GB26431@cisco.com>
References: <7347100B5761DC41A166AC17F22DF1122192830E@eusaamb103.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <7347100B5761DC41A166AC17F22DF1122192830E@eusaamb103.ericsson.se>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/bier/BrfS9EaV0Q7Llp7cPAAoO1NLz7I>
Cc: "BIER (bier@ietf.org)" <bier@ietf.org>
Subject: [Bier] draft-ietf-bier-oam-requirements-00: PMTUD requirement in BIER OAM Requirements
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2015 04:28:58 -0000

Thanks, Greg.

I was looking just for PMTU or MTU in the text and could not find it.

I do not agree to this requirement in the OAM requirement draft as of now.

Why is it needed for BIER ? AFAIK, there is no PMTUD for OAM
in any of the prior IP multicast transport options - native IP or MPLS. True ?
Any reason why BIER would need this more than those prior options ?
Any reason why BIER would make it a lot easier  than the prior options ?

This should IMHO be discussed in the draft.

If we get PMTUD, would it only be for OAM and only for the BIER path, eg:
not the end-to-end path ? If so, it should be called different (BP-MTUD or
the like). 

If someone proposes that it should be end-to-end, then this needs to go
back to MBoned, because it would ask to introduce PMTUD into eg: PIM path
segments.

Wrt. the protocols proposed in your PMTUD draft proposal: I would like
to understand why we would not want to proactively signal MTU intead
of probing it. There seems to have been some work in the past around
this in unicast, not sure how successful.

Cheers
    Toerless

On Fri, Nov 06, 2015 at 01:02:10AM +0000, Gregory Mirsky wrote:
> Hi Toerless,
> I'd like to bring requirement #9 in the BIER WG document OAM Requirements for BIER<https://tools.ietf.org/html/draft-ietf-bier-oam-requirements-00>:
> BIER OAM MUST support Path Maximum Transmission Unit discovery.
> Hope that addresses your question why are we doing PMTUD.
> 
>                 Regards,
>                                 Greg