From nobody Sun Jan 8 06:31:01 2017 Return-Path: X-Original-To: bier@ietf.org Delivered-To: bier@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B94EA129418; Sun, 8 Jan 2017 06:30:57 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.40.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148388585775.845.12121448847247750416.idtracker@ietfa.amsl.com> Date: Sun, 08 Jan 2017 06:30:57 -0800 Archived-At: Cc: bier@ietf.org Subject: [Bier] I-D Action: draft-ietf-bier-use-cases-04.txt X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2017 14:30:57 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Bit Indexed Explicit Replication of the IETF. Title : BIER Use Cases Authors : Nagendra Kumar Rajiv Asati Mach(Guoyi) Chen Xiaohu Xu Andrew Dolganow Tony Przygienda Arkadiy Gulko Dom Robinson Vishal Arya Caitlin Bestler Filename : draft-ietf-bier-use-cases-04.txt Pages : 17 Date : 2017-01-08 Abstract: Bit Index Explicit Replication (BIER) is an architecture that provides optimal multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain any multicast related per- flow state. BIER also does not require any explicit tree-building protocol for its operation. A multicast data packet enters a BIER domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs). The BFIR router adds a BIER header to the packet. The BIER header contains a bit-string in which each bit represents exactly one BFER to forward the packet to. The set of BFERs to which the multicast packet needs to be forwarded is expressed by setting the bits that correspond to those routers in the BIER header. This document describes some of the use-cases for BIER. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bier-use-cases/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-bier-use-cases-04 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-use-cases-04 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sun Jan 8 06:33:36 2017 Return-Path: X-Original-To: bier@ietfa.amsl.com Delivered-To: bier@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EBCC12947C for ; Sun, 8 Jan 2017 06:33:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.721 X-Spam-Level: X-Spam-Status: No, score=-17.721 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-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 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 VUbr88fyLIJm for ; Sun, 8 Jan 2017 06:33:33 -0800 (PST) Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A838812944E for ; Sun, 8 Jan 2017 06:33:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2792; q=dns/txt; s=iport; t=1483886013; x=1485095613; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=dC/1HQY4hd8msoDIcsYlhgLqT1s4rnySy1/MMdeeCsY=; b=GMB0fv3ThZon0/YGFEVYCImrwdGEh5Q45YiTXOnoIyzE3epFWgXdaQkc 4LB+IULAc+l1VUZ8QSTmoGtuiiVGroSK7jB55daDZTat3eX6K+BN+mo1t zjPFFVdPtjaTD0PzKU/mvKodnqmVJ7Mu/w4bUgSgnFAUeAK5I/RR3/nOR k=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DxAQDDTHJY/5xdJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzoBAQEBAR9fgQwHjVCnR4IKHwuFeAKBVj8UAQIBAQEBAQEBYx0?= =?us-ascii?q?LhGkCBAEBODQbAgEIEiQQJwsXDgIEEwmIZw6xZIoFAQEBAQEBAQECAQEBAQEBA?= =?us-ascii?q?QEgiyaDCYFvhTQFmxwBhliKdIF3UYQ3iV2KJ4gtAR84gUAVGB+GK3MBh1iBDQE?= =?us-ascii?q?BAQ?= X-IronPort-AV: E=Sophos;i="5.33,335,1477958400"; d="scan'208";a="368558779" Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jan 2017 14:33:32 +0000 Received: from XCH-ALN-015.cisco.com (xch-aln-015.cisco.com [173.36.7.25]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v08EXWj3031665 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Sun, 8 Jan 2017 14:33:32 GMT Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-ALN-015.cisco.com (173.36.7.25) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 8 Jan 2017 08:33:32 -0600 Received: from xch-rcd-015.cisco.com ([173.37.102.25]) by XCH-RCD-015.cisco.com ([173.37.102.25]) with mapi id 15.00.1210.000; Sun, 8 Jan 2017 08:33:32 -0600 From: "Nagendra Kumar Nainar (naikumar)" To: "bier@ietf.org" Thread-Topic: I-D Action: draft-ietf-bier-use-cases-04.txt Thread-Index: AQHSabvc/My8pkvkik63w7KkKapEJ6EutaSA Date: Sun, 8 Jan 2017 14:33:31 +0000 Message-ID: References: <148388585775.845.12121448847247750416.idtracker@ietfa.amsl.com> In-Reply-To: <148388585775.845.12121448847247750416.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.7.0.161029 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.82.172.37] Content-Type: text/plain; charset="us-ascii" Content-ID: <9BBCB662C4E67D428F02FDE6EC77D11F@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [Bier] I-D Action: draft-ietf-bier-use-cases-04.txt X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2017 14:33:35 -0000 Hi All, This is just a version bump to refresh the draft. Thanks, Nagendra On 1/8/17, 9:30 AM, "I-D-Announce on behalf of internet-drafts@ietf.org" wrote: > >A New Internet-Draft is available from the on-line Internet-Drafts >directories. >This draft is a work item of the Bit Indexed Explicit Replication of the >IETF. > > Title : BIER Use Cases > Authors : Nagendra Kumar > Rajiv Asati > Mach(Guoyi) Chen > Xiaohu Xu > Andrew Dolganow > Tony Przygienda > Arkadiy Gulko > Dom Robinson > Vishal Arya > Caitlin Bestler > Filename : draft-ietf-bier-use-cases-04.txt > Pages : 17 > Date : 2017-01-08 > >Abstract: > Bit Index Explicit Replication (BIER) is an architecture that > provides optimal multicast forwarding through a "BIER domain" without > requiring intermediate routers to maintain any multicast related per- > flow state. BIER also does not require any explicit tree-building > protocol for its operation. A multicast data packet enters a BIER > domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the > BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs). > The BFIR router adds a BIER header to the packet. The BIER header > contains a bit-string in which each bit represents exactly one BFER > to forward the packet to. The set of BFERs to which the multicast > packet needs to be forwarded is expressed by setting the bits that > correspond to those routers in the BIER header. > > This document describes some of the use-cases for BIER. > > >The IETF datatracker status page for this draft is: >https://datatracker.ietf.org/doc/draft-ietf-bier-use-cases/ > >There's also a htmlized version available at: >https://tools.ietf.org/html/draft-ietf-bier-use-cases-04 > >A diff from the previous version is available at: >https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-bier-use-cases-04 > > >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. > >Internet-Drafts are also available by anonymous FTP at: >ftp://ftp.ietf.org/internet-drafts/ > >_______________________________________________ >I-D-Announce mailing list >I-D-Announce@ietf.org >https://www.ietf.org/mailman/listinfo/i-d-announce >Internet-Draft directories: http://www.ietf.org/shadow.html >or ftp://ftp.ietf.org/ietf/1shadow-sites.txt From nobody Tue Jan 10 06:53:33 2017 Return-Path: X-Original-To: bier@ietf.org Delivered-To: bier@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DAA8F129D14; Tue, 10 Jan 2017 06:53:31 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.40.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148406001189.22126.7864258444764003894.idtracker@ietfa.amsl.com> Date: Tue, 10 Jan 2017 06:53:31 -0800 Archived-At: Cc: bier@ietf.org Subject: [Bier] I-D Action: draft-ietf-bier-mvpn-05.txt X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 14:53:32 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Bit Indexed Explicit Replication of the IETF. Title : Multicast VPN Using BIER Authors : Eric C. Rosen Mahesh Sivakumar Sam K Aldrin Andrew Dolganow Tony Przygienda Filename : draft-ietf-bier-mvpn-05.txt Pages : 13 Date : 2017-01-10 Abstract: The Multicast Virtual Private Network (MVPN) specifications require the use of multicast tunnels ("P-tunnels") that traverse a Service Provider's backbone network. The P-tunnels are used for carrying multicast traffic across the backbone. A variety of P-tunnel types are supported. Bit Index Explicit Replication (BIER) is a new architecture that provides optimal multicast forwarding through a "multicast domain", without requiring intermediate routers to maintain any per-flow state or to engage in an explicit tree-building protocol. This document specifies the protocol and procedures that allow MVPN to use BIER as the method of carrying multicast traffic over an SP backbone network. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bier-mvpn/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-bier-mvpn-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-mvpn-05 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Jan 10 11:09:07 2017 Return-Path: X-Original-To: bier@ietfa.amsl.com Delivered-To: bier@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55643129576 for ; Tue, 10 Jan 2017 11:09:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 aRg6vzhwtOej for ; Tue, 10 Jan 2017 11:08:59 -0800 (PST) Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2952B12952C for ; Tue, 10 Jan 2017 11:08:57 -0800 (PST) Received: by mail-qk0-x235.google.com with SMTP id u25so568918334qki.2 for ; Tue, 10 Jan 2017 11:08:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=rQwLAJVcDS5IvvubWHWdzF9HcnQbAgWM5K8Yz0Ufti8=; b=oaAomkwwzH0Nl6H49jTOyP5qQ6NGaLMRpvAlojaZZAkXjUyDwdEvBk+A3Ezp6sZfcX G2gFiJLVqMz8aXEdJiSv8k1DrRO19rEF7fvN3H3n49EIbKhfRwsCu1XJ+rX1ZM2jyb2f KW3TnDrmT19r1TqjfeQZ7S+hUkiQ56qCUfvCVJHVeCawbmm7kuHc8ZT8YGmL3gD1kKqA QnxNO3pEGDSLAEnhiSRMm+rExGZab0APlYI9wYyZFTYNTrVn2iJnjjYs/N+EMHltDC1b 5WdRTGACwhLCu+uQUSsiLPhpeqW5UtD/RQ/EUExKZMl8Xnpps2Gxu4bUllrLWNoqtKqq sVGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=rQwLAJVcDS5IvvubWHWdzF9HcnQbAgWM5K8Yz0Ufti8=; b=gef2DTKhfYEPLyBaPa1vFCCtR3/c4MZG2W7V3wptCIUMfRwQSfY3hOmnfbNtRop4tq Wlp8ifpZSrRk30Huk4TawmH7Zpham0LDKVvPYnzLN+WRyc9LW8iumDgJkitnxoUPsSXM 5R29WgjG6O5RV3UnkmtKBSbfbgTCfunLfnGe8UIcQCaCAAFbkusQPUgczIJKd6FKaZf5 DaiV6zfSsAciEah169C8SCZQYnpQMZOyz5mV383g9vmgGYD85b6Q0T0hDaFph3bsErbs ncTd5vBGVeqnAHAk9NrShXAIaW31dg+biYNTVQ7bcy5pdCry/0xVddo8BssGMfen4jvM fqog== X-Gm-Message-State: AIkVDXKQL3g+2K6ltTCMWnpASs9aRqrHlWp8yI8GBOfRJFPyOlaiNsVf9e3kqA6YOLI6a8oQySA3QCny3OhWbA== X-Received: by 10.55.39.193 with SMTP id n184mr4406097qkn.315.1484075336305; Tue, 10 Jan 2017 11:08:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.37.250 with HTTP; Tue, 10 Jan 2017 11:08:55 -0800 (PST) In-Reply-To: References: From: Greg Shepherd Date: Tue, 10 Jan 2017 11:08:55 -0800 Message-ID: To: "Jeffrey (Zhaohui) Zhang" Content-Type: multipart/alternative; boundary=94eb2c0949083d92bf0545c237a3 Archived-At: Cc: "bier@ietf.org" Subject: Re: [Bier] Call for WG adoption: draft-chenvgovindan-bier-bgp-ls-bier-ext-01 X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: gjshep@gmail.com List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 19:09:02 -0000 --94eb2c0949083d92bf0545c237a3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable WG, Looks like we have strong support for WG adoption of this draft. Authors, please update the name in tools and status as a WG doc. Thanks, Greg On Mon, Dec 12, 2016 at 5:19 PM, Jeffrey (Zhaohui) Zhang wrote: > I support the adoption, but the document should clearly describe the use > case. > > > > The IGP extensions for BIER signals the following information: > > > > - BFR-IDs > > - BIER labels (in the form of label ranges) > > > > On the surface, it seems to be useful to feed the information to a > controller (hence the support for adoption). However, in an environment > where a controller is collecting the information, most likely the > controller itself (or some siblings) is allocating the BFR-IDs? It=E2=80= =99s not > clear how the collected label ranges could be used either. > > > > I assume there is a good use case for this =E2=80=93 just need to be docu= mented, > sooner than later. > > > > Jeffrey > > > > > > On Thu, Dec 8, 2016 at 9:39 AM, Greg Shepherd wrote: > > BIER WG, > > > > This message begins the call for adoption of: > > > > https://datatracker.ietf.org/doc/draft-chenvgovindan-bier-bgp-ls-bier-ext= / > > > > Please read and reply to this thread. End of call will be Dec 22, 2016 > > > > Cheers, > > Chairs. > > > _______________________________________________ > BIER mailing list > BIER@ietf.org > https://www.ietf.org/mailman/listinfo/bier > > > > _______________________________________________ > BIER mailing list > BIER@ietf.org > https://www.ietf.org/mailman/listinfo/bier > > --94eb2c0949083d92bf0545c237a3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
WG,

Looks like we have strong support f= or WG adoption of this draft. Authors, please update the name in tools and = status as a WG doc.

Thanks,
Greg

On Mon, Dec 1= 2, 2016 at 5:19 PM, Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>= wrote:

I support the adoption, but the docum= ent should clearly describe the use case.

=C2=A0

The IGP extensions for BIER signals t= he following information:

=C2=A0

-=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 BFR-IDs

-=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 BIER labels (in the form of labe= l ranges)

=C2=A0

On the surface, it seems to be useful= to feed the information to a controller (hence the support for adoption). = However, in an environment where a controller is collecting the information, most l= ikely the controller itself (or some siblings) is allocating the BFR-IDs? I= t=E2=80=99s not clear how the collected label ranges could be used either.<= u>

=C2=A0

I assume there is a good use case for= this =E2=80=93 just need to be documented, sooner than later.

=

=C2=A0

Jeffrey

<= span style=3D"font-size:11.0pt;font-family:"Calibri",sans-serif;c= olor:#1f497d">=C2=A0

=C2=A0

On Thu, Dec 8, 2016 at 9:39 AM, Greg Shepherd <gjshep@gmail.com>= ; wrote:

BIER WG,

=C2=A0

This message begins the call for adoption of:=

=C2=A0

=C2=A0

Please read and reply to this thread. End of call wi= ll be Dec 22, 2016

=C2=A0

Cheers,

Chairs.


_______________________________________________
BIER mailing list
BIER@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/bier

=C2=A0


_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier


--94eb2c0949083d92bf0545c237a3-- From nobody Tue Jan 10 11:09:44 2017 Return-Path: X-Original-To: bier@ietfa.amsl.com Delivered-To: bier@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72D5B12952C for ; Tue, 10 Jan 2017 11:09:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 TExRx3vchiTv for ; Tue, 10 Jan 2017 11:09:41 -0800 (PST) Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBD6F128B38 for ; Tue, 10 Jan 2017 11:09:38 -0800 (PST) Received: by mail-qt0-x22e.google.com with SMTP id l7so125807746qtd.1 for ; Tue, 10 Jan 2017 11:09:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:from:date:message-id:subject:to; bh=Ap+FBA5OwoZCtJDQwTjn5Bgpcy7Mli/nqDWiaUe/+98=; b=eSFu5QVel9FY3ZpzcevVqGwH3GclV8HsZudOJJlMp/Z3sEAKCR16ZmuzIKYQS4n/dm 4x8si7VN6cDbyIL5cSwS+adtemUljlOlqPT6hhn4hr7RpO3PgqZsnBgUBEFMoCxkX3m0 ELof8IFP7abHEAmap2nqonbldSi/j8+6ypBUBR1iDnUHOdERzEaUayan82sHSmNUG3vU d0m2idxBnmKIC+kePoYcx0gyW6grWlOV09jXNyM62E2xZe5zj7Czta0HI4BUeVHVA50g 7raljf216eL8eHHh77fHFHex15W2pebm47kSz/mJBs/88z7BHkGbsmI8ctaxFDsb+JfP 0SGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:from:date:message-id :subject:to; bh=Ap+FBA5OwoZCtJDQwTjn5Bgpcy7Mli/nqDWiaUe/+98=; b=NJNDix8tf5tSPR/QjK7Z4ZwY2Rfuqq8NGq+aiWhm41WKRtyOFFnwddun8IIoxFRFR3 0UgcuFulPqbcyMTY+HeHUP23tEhK7ebrLLBFmPLJuD+B7HcS1/SKOXH5e+wl7WjFWVdn eWIV6897SPSNgQfTV/2hFV+2DJt74Pa8quQ1yx3hxdn5HoK8fL/8WB1oy8cmbzkc8UK4 n4krR+NeabDLOkoc7oKjf4Vg9whi4odebOZMD5RdstO2ZOIUja74Oisgt5eJAXe6O+d2 ZXEPMnRUuQM0CGXKmFx58kuMcyaWwoHFTbljrP1UKwEX6Hqky10PkDkYTvrNaGPiCW9v aSsw== X-Gm-Message-State: AIkVDXKd6mJ1uAM8LzrlgDitBhW0X1N2L0lRBrftb+S3rGMqqjFw3kYQRPrQ+WVt61iDwpyAMDjjDeKDldlQbw== X-Received: by 10.200.38.196 with SMTP id 4mr1965499qtp.96.1484075377840; Tue, 10 Jan 2017 11:09:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.37.250 with HTTP; Tue, 10 Jan 2017 11:09:37 -0800 (PST) From: Greg Shepherd Date: Tue, 10 Jan 2017 11:09:37 -0800 Message-ID: To: "bier@ietf.org" Content-Type: multipart/alternative; boundary=001a113f4790b758b90545c23973 Archived-At: Subject: [Bier] Pre-IETF98 Work X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: gjshep@gmail.com List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jan 2017 19:09:43 -0000 --001a113f4790b758b90545c23973 Content-Type: text/plain; charset=UTF-8 *, There are several expiring WG drafts which need to be addressed. Let's take a look at these and see if any of them represent complete work. At our last meeting it was suggested that we potentially have docs which could be advanced to WGLC, but wouldn't have to go into the Editor's Queue yet, pending the WG's completion of the reqs to recharter all of our work into the Proposed Standards track. I suggest we start with this list of expiring docs to either advance to WGLC or rev/refresh as necessary: draft-ietf-bier-architecture draft-ietf-bier-isis-extensions draft-ietf-bier-ospf-extensions draft-ietf-bier-ping draft-ietf-bier-pmmm-oam draft-ietf-bier-path-mtu-discovery The MPLS encap draft: https://datatracker.ietf.org/doc/draft-ietf-bier-mpls-encapsulation/ ..should now represent the consensus on our unified encapsulation. This too could be a candidate for WGLC MVPN draft was just rev'd: https://datatracker.ietf.org/doc/draft-ietf-bier-mvpn/ Please read and respond to the list with any issues. Thanks, Chairs (Greg) --001a113f4790b758b90545c23973 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
*,

There are several expiring WG drafts= which need to be addressed. Let's take a look at these and see if any = of them represent complete work. At our last meeting it was suggested that = we potentially have docs which could be advanced to WGLC, but wouldn't = have to go into the Editor's Queue yet, pending the WG's completion= of the reqs to recharter all of our work into the Proposed Standards track= .

I suggest we start with this list of expiring do= cs to either advance to WGLC or rev/refresh as necessary:

draft-ietf-bier-architecture
draft-ietf-bier-isis-extensi= ons
draft-ietf-bier-ospf-extensions
draft-ietf-bier-ping
draft-ietf-bier-pmmm-oam
draft-ietf-bier-path-mtu-discovery

The MPLS encap draft:
..should now represent= the consensus on our unified encapsulation. This too could be a candidate = for WGLC

MVPN draft was just rev'd:
Please rea= d and respond to the list with any issues.

Thanks,=
Chairs
(Greg)


--001a113f4790b758b90545c23973-- From nobody Tue Jan 10 19:57:15 2017 Return-Path: X-Original-To: bier@ietfa.amsl.com Delivered-To: bier@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AFC91295C5 for ; Tue, 10 Jan 2017 19:57:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 fdAuwwT_XEvP for ; Tue, 10 Jan 2017 19:57:12 -0800 (PST) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04F2C12952F for ; Tue, 10 Jan 2017 19:57:12 -0800 (PST) Received: by mail-oi0-x232.google.com with SMTP id w204so74522051oiw.0 for ; Tue, 10 Jan 2017 19:57:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zYxNsb2jSJmAwAx8CYPDZgSw0nfw1HgI6YqeTYBVFj4=; b=BaIjLEaCIv7O1RFTg4fJwYRig53kTYKpUDsUzxr9JnXPa1p7ltqmZsvTRdbvvP/6X9 DKvsalvClWXXD+RtjGjoDQAFOZCy5Xf+cOgisXCxi+oFko4LrPotl0wz6mr2zFDEfdW1 dFyMYjstrwZmjwRXgDdlbSu4FKf73ajp9O3jhzs4QFVdnwggIdHG4BxbBJys4gM9DHc1 kA221eBh98ZYgsTNgKTo+U2zc/+y205YjZTslRvMk66xMSR6jbqwDNxoBhxSqhzTtI/k uGX8AHD7oU0LtlEtpKJvpPmA9TH5UArflUbIi2u7pCI462DLbWb3VBrkG53Oz1LZr6Oz H01Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zYxNsb2jSJmAwAx8CYPDZgSw0nfw1HgI6YqeTYBVFj4=; b=WONRTgnnkKEY+o8fBs8VZLh26QzhHedavYiIYwBwoDcjC1EHrHsWsfEUGtURbz3FBb /wyqd/g/She/sFWtdBwCYlu8LOt3w6FFA9jHKbyfzRHHGu1ZKOBbyt1zce1ACRetlRIw TqL9un/BQcohTsIVuwS26p52HeJeuE5asQoBjjGGP60PPQ60Hb9O8z/cx+4ND4jw8lCm bqb8TQVKQWqKE6JEvO5qHj/dqZCASjRvacQfMXGeHo2xGwRZNO2VD5yjXbPB/WNFWh7F svhx52uV9SSL7B38IBfMTkwje7q+V9nftcHBVOMUbeIuYqzvrcEEpgqng18mg/7maKx3 vxzA== X-Gm-Message-State: AIkVDXJfcrUH855Ykcvvf0/vTohLyW4imFUmCx/XNSmpuQX1wD7K88YCknmAZ/OscTQWFHF0Zk6G+5mrDk6tIQ== X-Received: by 10.202.232.80 with SMTP id f77mr2923898oih.60.1484107031342; Tue, 10 Jan 2017 19:57:11 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.1.103 with HTTP; Tue, 10 Jan 2017 19:57:10 -0800 (PST) In-Reply-To: References: From: Greg Mirsky Date: Tue, 10 Jan 2017 19:57:10 -0800 Message-ID: To: Greg Shepherd Content-Type: multipart/alternative; boundary=001a1140831e6974000545c99833 Archived-At: Cc: "bier@ietf.org" Subject: Re: [Bier] Pre-IETF98 Work X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 03:57:13 -0000 --001a1140831e6974000545c99833 Content-Type: text/plain; charset=UTF-8 Hi Greg, et. al, I'll refresh draft-ietf-bier-pmmm-oam and draft-ietf-bier-path-mtu-discovery shortly.Would WG Chairs consider adding draft-ietf-bier-oam-requirements to the list of candidates? Regards, Greg On Tue, Jan 10, 2017 at 11:09 AM, Greg Shepherd wrote: > *, > > There are several expiring WG drafts which need to be addressed. Let's > take a look at these and see if any of them represent complete work. At our > last meeting it was suggested that we potentially have docs which could be > advanced to WGLC, but wouldn't have to go into the Editor's Queue yet, > pending the WG's completion of the reqs to recharter all of our work into > the Proposed Standards track. > > I suggest we start with this list of expiring docs to either advance to > WGLC or rev/refresh as necessary: > > draft-ietf-bier-architecture > draft-ietf-bier-isis-extensions > draft-ietf-bier-ospf-extensions > draft-ietf-bier-ping > draft-ietf-bier-pmmm-oam > draft-ietf-bier-path-mtu-discovery > > The MPLS encap draft: > https://datatracker.ietf.org/doc/draft-ietf-bier-mpls-encapsulation/ > ..should now represent the consensus on our unified encapsulation. This > too could be a candidate for WGLC > > MVPN draft was just rev'd: > https://datatracker.ietf.org/doc/draft-ietf-bier-mvpn/ > Please read and respond to the list with any issues. > > Thanks, > Chairs > (Greg) > > > > _______________________________________________ > BIER mailing list > BIER@ietf.org > https://www.ietf.org/mailman/listinfo/bier > > --001a1140831e6974000545c99833 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Greg, et. al,
I'll refresh=C2=A0draft-ietf-bier-pmmm-oam and=C2=A0draft-= ietf-bier-path-mtu-discovery shortly.Would WG Chairs = consider adding draft-ietf-bier-oam-requirements to the list of candidates?=

Regards,
Greg

On Tue, Jan 10, 2017 at 11:09 AM, Greg Shepherd <gjshe= p@gmail.com> wrote:
*,

There are several expiring WG drafts which = need to be addressed. Let's take a look at these and see if any of them= represent complete work. At our last meeting it was suggested that we pote= ntially have docs which could be advanced to WGLC, but wouldn't have to= go into the Editor's Queue yet, pending the WG's completion of the= reqs to recharter all of our work into the Proposed Standards track.
=

I suggest we start with this list of expiring docs to e= ither advance to WGLC or rev/refresh as necessary:

draft-ietf-bier-architecture
draft-ietf-bier-isis-extension= s
draft-ietf-bier-ospf-extensions
draft-ietf-bier-ping
draft-ietf-bier-pmmm-oam
draft-ietf-<= /span>bier-path-mtu-discovery

= The MPLS encap draft:=
..should now represent the consensus on= our unified encapsulation. This too could be a candidate for WGLC

MVPN draft was just rev'd:
Plea= se read and respond to the list with any issues.

T= hanks,
Chairs
(Greg)



_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier


--001a1140831e6974000545c99833-- From nobody Tue Jan 10 23:46:23 2017 Return-Path: X-Original-To: bier@ietfa.amsl.com Delivered-To: bier@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6CCB129A57 for ; Tue, 10 Jan 2017 23:46:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.72 X-Spam-Level: X-Spam-Status: No, score=-17.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-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 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 8GikXGl4-D3w for ; Tue, 10 Jan 2017 23:46:19 -0800 (PST) Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18F7A129A4E for ; Tue, 10 Jan 2017 23:46:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8822; q=dns/txt; s=iport; t=1484120778; x=1485330378; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=iw195NkSD3k6h8OwoeEDU7/9gIHOMVIN1huAiyytyiQ=; b=G7q7vXS7gSY4hFaVgTpOjBRQYWhtiVgD/PqgP3APoCKgS78X3X0NUEEm F6OSSu1eUzgJEY2wp8OqbJcZ/kjfhxwCLZCunTxGMJ71EOUObLJc4Vu9I 7RRL7dNvQwN1jWUHqICjwSXcrQvxEmw7oZ3U/fWmwkzGCUL25zuibYhZE Q=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AcAQBX4nVY/4cNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgnFKAQEBAQEfX4ENB41QkieHf4d9hSuCCx8BCoV4AoIKPxQBAgE?= =?us-ascii?q?BAQEBAQFjKIRpAQEBBAEBbAsQAgEIEQECAQIoByEGCxQDBggCBAENBYhlAxgOs?= =?us-ascii?q?lKHQg2CSAEBAQEBAQEBAQEBAQEBAQEBAQEBARgFiyaCToIYhUYFmnE4AYZahni?= =?us-ascii?q?Df4F3hQyDTYYVig2IUwEfOIFBFTqDfIIzc4dZgQ0BAQE?= X-IronPort-AV: E=Sophos;i="5.33,345,1477958400"; d="scan'208,217";a="370304830" Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Jan 2017 07:46:18 +0000 Received: from XCH-RCD-013.cisco.com (xch-rcd-013.cisco.com [173.37.102.23]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v0B7kIXq019113 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 11 Jan 2017 07:46:18 GMT Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-RCD-013.cisco.com (173.37.102.23) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 11 Jan 2017 01:46:17 -0600 Received: from xch-rcd-015.cisco.com ([173.37.102.25]) by XCH-RCD-015.cisco.com ([173.37.102.25]) with mapi id 15.00.1210.000; Wed, 11 Jan 2017 01:46:17 -0600 From: "Nagendra Kumar Nainar (naikumar)" To: Greg Mirsky , Greg Shepherd Thread-Topic: [Bier] Pre-IETF98 Work Thread-Index: AQHSa3UfaAtWB3NTyUea8c8pg2PUvqEzCzwA///sLYA= Date: Wed, 11 Jan 2017 07:46:17 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.7.0.161029 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.82.221.109] Content-Type: multipart/alternative; boundary="_000_D49B4CD91C6D01naikumarciscocom_" MIME-Version: 1.0 Archived-At: Cc: "bier@ietf.org" Subject: Re: [Bier] Pre-IETF98 Work X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 07:46:21 -0000 --_000_D49B4CD91C6D01naikumarciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Greg S, I will refresh draft-ietf-bier-ping soon. Thanks, Nagendra From: BIER > on behalf = of Greg Mirsky > Date: Tuesday, January 10, 2017 at 10:57 PM To: Greg Shepherd > Cc: "bier@ietf.org" > Subject: Re: [Bier] Pre-IETF98 Work Hi Greg, et. al, I'll refresh draft-ietf-bier-pmmm-oam and draft-ietf-bier-path-mtu-discover= y shortly.Would WG Chairs consider adding draft-ietf-bier-oam-requirements = to the list of candidates? Regards, Greg On Tue, Jan 10, 2017 at 11:09 AM, Greg Shepherd > wrote: *, There are several expiring WG drafts which need to be addressed. Let's take= a look at these and see if any of them represent complete work. At our las= t meeting it was suggested that we potentially have docs which could be adv= anced to WGLC, but wouldn't have to go into the Editor's Queue yet, pending= the WG's completion of the reqs to recharter all of our work into the Prop= osed Standards track. I suggest we start with this list of expiring docs to either advance to WGL= C or rev/refresh as necessary: draft-ietf-bier-architecture draft-ietf-bier-isis-extensions draft-ietf-bier-ospf-extensions draft-ietf-bier-ping draft-ietf-bier-pmmm-oam draft-ietf-bier-path-mtu-discovery The MPLS encap draft: https://datatracker.ietf.org/doc/draft-ietf-bier-mpls-encapsulation/ ..should now represent the consensus on our unified encapsulation. This too= could be a candidate for WGLC MVPN draft was just rev'd: https://datatracker.ietf.org/doc/draft-ietf-bier-mvpn/ Please read and respond to the list with any issues. Thanks, Chairs (Greg) _______________________________________________ BIER mailing list BIER@ietf.org https://www.ietf.org/mailman/listinfo/bier --_000_D49B4CD91C6D01naikumarciscocom_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable
Hi Greg S,

I will refresh draft-ietf-bier-ping soon.

Thanks,
Nagendra

From: BIER <bier-bounces@ietf.org> on behalf of Greg Mirsky= <gregimirsky@gmail.com>=
Date: Tuesday, January 10, 2017 at = 10:57 PM
To: Greg Shepherd <gjshep@gmail.com>
Cc: "bier@ietf.org" <bier@i= etf.org>
Subject: Re: [Bier] Pre-IETF98 Work=

Hi Greg, et. al,
I'll refresh draft-ietf-<= span class=3D"gmail-m_-8008663869028370559gmail-il" style=3D"font-size:12.8= px">bier-pmmm-oam and <= span style=3D"font-size:12.8px">draft-ietf-bier-path-mtu-d= iscovery shortly.Would WG Chairs consider adding draft-ietf-bier-oam-requirements t= o the list of candidates?

Regards,
Greg

On Tue, Jan 10, 2017 at 11:09 AM, Greg Shepherd = <gjshep@gmail.com<= /a>> wrote:
*,

There are several expiring WG drafts which need to be addressed. Let's= take a look at these and see if any of them represent complete work. At ou= r last meeting it was suggested that we potentially have docs which could b= e advanced to WGLC, but wouldn't have to go into the Editor's Queue yet, pending the WG's completion of the= reqs to recharter all of our work into the Proposed Standards track.

I suggest we start with this list of expiring docs to either advance t= o WGLC or rev/refresh as necessary:

draft-ietf-bier-architecture
draft-ietf-bier-isis-extensions
draft-ietf-bier-ospf-extensions
draft-ietf-bier-ping
draft-ietf-bier-pmmm-oam=
draft-ietf-bier-path-mtu= -discovery

The MPLS encap draft:
..should now represent the consensus on our unified encapsulation. Thi= s too could be a candidate for WGLC

MVPN draft was just rev'd:
Please read and respond to the list with any issues.

Thanks,
Chairs
(Greg)



_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier


 --_000_D49B4CD91C6D01naikumarciscocom_-- From nobody Thu Jan 12 10:06:20 2017 Return-Path: X-Original-To: bier@ietfa.amsl.com Delivered-To: bier@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB31128AB0 for ; Thu, 12 Jan 2017 10:06:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Ms6h9YP5dgFs for ; Thu, 12 Jan 2017 10:06:09 -0800 (PST) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D71E512950F for ; Thu, 12 Jan 2017 10:06:07 -0800 (PST) Received: by mail-qk0-x22b.google.com with SMTP id u25so28917520qki.2 for ; Thu, 12 Jan 2017 10:06:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=f/Y+N+B1znTOoHr3wVPb4nuY8KwOXHKQU7mVzfOcEMA=; b=gUH59V/n5FfBg1Rr3W3VEZeNysn/tA9O5kYz5l+qd2EZ5Z08UCSiDt6juwYREzOKwA D7N747db/vffpQ2njJM8K0Ce7+ve4ZlX+lFtsDv3CEpjEDpZjjRcEis4ABCkRb15yDm3 bJRXgdY/6OQpxlFw/D4Pj6GLiHBGiTolpHcmhmnNSJdM3i4s4O+Mv8FfN8P7Et9R18yb jtNVNHisn0QVrxreIxweOHEXmIXMZDSpiKztXysidqwK7b48maLWoKdb0KKxdwLWWxCT TrGf7Po95YUMxTLVjAfAIgUpy5q17i+V78N1ZU7TuOXXjLcdKjt2bBzd0jedZfNPVbXb QFHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=f/Y+N+B1znTOoHr3wVPb4nuY8KwOXHKQU7mVzfOcEMA=; b=ouOT8eGjLQvZP9sWx3PZ2YpONtDXxjhSddwEL4ctYCgoOgW6OJebMgODDvTzhwI1cX vm2tXlrlJqDINSLlvkPm4/isU3++PLh848p7H/fTZfzSOLFgfxOXTLMLbXTlb8Qus8pD kh+JfcdfMzaFRC5vUwdaOPCtMAvJNQUgGyL/XwW+xpVhldztX2Ogc8U1usgrAfwbIeVg qhcTDHSr++A9w7q8gJmf3IvY3iNKtjgFBrnRqV+3tisG66Au98AHWmjUhtlZ0hxxMzU9 FRkd/whSdi5+NJCU9g9LpF6iz3W+GjJuyMzIYHxxVhgMD5nM5S50I9aVUzLA1SYddrVH nEXQ== X-Gm-Message-State: AIkVDXLb4Dxp85lHRMDObiUy+CdjnifwpeWlA9G7HvKSU2+osVoiSxZgSvRRREUSZRbqeTvNMRnoLd+SHjVV9w== X-Received: by 10.55.78.73 with SMTP id c70mr15510916qkb.11.1484244366963; Thu, 12 Jan 2017 10:06:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.42.124 with HTTP; Thu, 12 Jan 2017 10:06:06 -0800 (PST) In-Reply-To: References: From: Greg Shepherd Date: Thu, 12 Jan 2017 10:06:06 -0800 Message-ID: To: Greg Mirsky Content-Type: multipart/alternative; boundary=001a114a7f0e40bb7a0545e992c7 Archived-At: Cc: "bier@ietf.org" Subject: Re: [Bier] Pre-IETF98 Work X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: gjshep@gmail.com List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 18:06:11 -0000 --001a114a7f0e40bb7a0545e992c7 Content-Type: text/plain; charset=UTF-8 Thanks Greg. Will do. Greg On Tue, Jan 10, 2017 at 7:57 PM, Greg Mirsky wrote: > Hi Greg, et. al, > I'll refresh draft-ietf-bier-pmmm-oam and draft-ietf-bier-path-mtu-discovery > shortly.Would WG Chairs consider adding draft-ietf-bier-oam-requirements > to the list of candidates? > > Regards, > Greg > > On Tue, Jan 10, 2017 at 11:09 AM, Greg Shepherd wrote: > >> *, >> >> There are several expiring WG drafts which need to be addressed. Let's >> take a look at these and see if any of them represent complete work. At our >> last meeting it was suggested that we potentially have docs which could be >> advanced to WGLC, but wouldn't have to go into the Editor's Queue yet, >> pending the WG's completion of the reqs to recharter all of our work into >> the Proposed Standards track. >> >> I suggest we start with this list of expiring docs to either advance to >> WGLC or rev/refresh as necessary: >> >> draft-ietf-bier-architecture >> draft-ietf-bier-isis-extensions >> draft-ietf-bier-ospf-extensions >> draft-ietf-bier-ping >> draft-ietf-bier-pmmm-oam >> draft-ietf-bier-path-mtu-discovery >> >> The MPLS encap draft: >> https://datatracker.ietf.org/doc/draft-ietf-bier-mpls-encapsulation/ >> ..should now represent the consensus on our unified encapsulation. This >> too could be a candidate for WGLC >> >> MVPN draft was just rev'd: >> https://datatracker.ietf.org/doc/draft-ietf-bier-mvpn/ >> Please read and respond to the list with any issues. >> >> Thanks, >> Chairs >> (Greg) >> >> >> >> _______________________________________________ >> BIER mailing list >> BIER@ietf.org >> https://www.ietf.org/mailman/listinfo/bier >> >> > --001a114a7f0e40bb7a0545e992c7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks Greg. Will do.

Greg
<= div class=3D"gmail_extra">
On Tue, Jan 10, 20= 17 at 7:57 PM, Greg Mirsky <gregimirsky@gmail.com> wrote= :
Hi Greg, et. al,
I= 'll refresh=C2=A0draft-ietf-bier-pmmm-oam and=C2=A0draft-ietf-<= span class=3D"m_3346397891516021312gmail-m_-8008663869028370559gmail-il" st= yle=3D"font-size:12.8px">bier-path-= mtu-discovery shortly.Would WG= Chairs consider adding draft-ietf-bier-oam-requirements to the list o= f candidates?

=
Regards,
Greg

On Tue, Jan 10, 20= 17 at 11:09 AM, Greg Shepherd <gjshep@gmail.com> wrote:
*,

There are several expiring WG drafts which need= to be addressed. Let's take a look at these and see if any of them rep= resent complete work. At our last meeting it was suggested that we potentia= lly have docs which could be advanced to WGLC, but wouldn't have to go = into the Editor's Queue yet, pending the WG's completion of the req= s to recharter all of our work into the Proposed Standards track.

I suggest we start with this list of expiring docs to eithe= r advance to WGLC or rev/refresh as necessary:

dra= ft-ietf-bier-architecture
draft-ietf-bier-isis-extensions
draft-ietf-bier-ospf-extensions
draft-ietf-bier-ping<= br>
draft-ietf-bier-pmmm-oam
draft-ietf-bier-path-mtu-discovery

The MPLS encap draft:
..should now represent the consensus on our unified enca= psulation. This too could be a candidate for WGLC

= MVPN draft was just rev'd:
Please read and respo= nd to the list with any issues.

Thanks,
= Chairs
(Greg)



_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier



--001a114a7f0e40bb7a0545e992c7-- From nobody Tue Jan 17 08:47:20 2017 Return-Path: X-Original-To: bier@ietf.org Delivered-To: bier@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ED09C127077; Tue, 17 Jan 2017 08:47:14 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.40.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148467163492.32111.801448843498983789.idtracker@ietfa.amsl.com> Date: Tue, 17 Jan 2017 08:47:14 -0800 Archived-At: Cc: bier@ietf.org Subject: [Bier] I-D Action: draft-ietf-bier-oam-requirements-03.txt X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2017 16:47:15 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Bit Indexed Explicit Replication of the IETF. Title : Operations, Administration and Maintenance (OAM) Requirements for Bit Index Explicit Replication (BIER) Layer Authors : Greg Mirsky Erik Nordmark Carlos Pignataro Nagendra Kumar Sam Aldrin Lianshu Zheng Mach Chen Nobo Akiya Santosh Pallagatti Filename : draft-ietf-bier-oam-requirements-03.txt Pages : 6 Date : 2017-01-16 Abstract: This document describes a list of functional requirement toward Operations, Administration and Maintenance (OAM) toolset in Bit Index Explicit Replication (BIER) layer of a network. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bier-oam-requirements/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-bier-oam-requirements-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-oam-requirements-03 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Jan 17 09:11:32 2017 Return-Path: X-Original-To: bier@ietf.org Delivered-To: bier@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AA61112958A; Tue, 17 Jan 2017 09:11:27 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.40.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148467308767.31979.417713823811206793.idtracker@ietfa.amsl.com> Date: Tue, 17 Jan 2017 09:11:27 -0800 Archived-At: Cc: bier@ietf.org Subject: [Bier] I-D Action: draft-ietf-bier-ping-01.txt X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2017 17:11:27 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Bit Indexed Explicit Replication of the IETF. Title : BIER Ping and Trace Authors : Nagendra Kumar Carlos Pignataro Nobo Akiya Lianshu Zheng Mach Chen Greg Mirsky Filename : draft-ietf-bier-ping-01.txt Pages : 26 Date : 2017-01-17 Abstract: Bit Index Explicit Replication (BIER) is an architecture that provides optimal multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain any multicast related per- flow state. BIER also does not require any explicit tree-building protocol for its operation. A multicast data packet enters a BIER domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs). The BFIR router adds a BIER header to the packet. The BIER header contains a bit-string in which each bit represents exactly one BFER to forward the packet to. The set of BFERs to which the multicast packet needs to be forwarded is expressed by setting the bits that correspond to those routers in the BIER header. This document describes the mechanism and basic BIER OAM packet format that can be used to perform failure detection and isolation on BIER data plane. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bier-ping/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-bier-ping-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-ping-01 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Jan 17 11:36:44 2017 Return-Path: X-Original-To: bier@ietf.org Delivered-To: bier@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BA1C12947E; Tue, 17 Jan 2017 11:36:39 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.40.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148468179960.32094.14556564442578481293.idtracker@ietfa.amsl.com> Date: Tue, 17 Jan 2017 11:36:39 -0800 Archived-At: Cc: bier@ietf.org Subject: [Bier] I-D Action: draft-ietf-bier-path-mtu-discovery-01.txt X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jan 2017 19:36:39 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Bit Indexed Explicit Replication of the IETF. Title : Path Maximum Transmission Unit Discovery (PMTUD) for Bit Index Explicit Replication (BIER) Layer Authors : Greg Mirsky Tony Przygienda Andrew Dolganow Filename : draft-ietf-bier-path-mtu-discovery-01.txt Pages : 8 Date : 2017-01-17 Abstract: This document describes Path Maximum Transmission Unit Discovery (PMTUD) in Bit Indexed Explicit Replication (BIER) layer. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bier-path-mtu-discovery/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-bier-path-mtu-discovery-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-path-mtu-discovery-01 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Jan 17 23:18:02 2017 Return-Path: X-Original-To: bier@ietf.org Delivered-To: bier@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 856A61293E8; Tue, 17 Jan 2017 23:18:00 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.40.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148472388054.32106.2730375319141268670.idtracker@ietfa.amsl.com> Date: Tue, 17 Jan 2017 23:18:00 -0800 Archived-At: Cc: bier@ietf.org Subject: [Bier] I-D Action: draft-ietf-bier-idr-extensions-02.txt X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2017 07:18:00 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Bit Indexed Explicit Replication of the IETF. Title : BGP Extensions for BIER Authors : Xiaohu Xu Mach Chen Keyur Patel IJsbrand Wijnands Antoni Przygienda Filename : draft-ietf-bier-idr-extensions-02.txt Pages : 7 Date : 2017-01-17 Abstract: Bit Index Explicit Replication (BIER) is a new multicast forwarding architecture which doesn't require an explicit tree-building protocol and doesn't require intermediate routers to maintain any multicast state. BIER is applicable in a multi-tenant data center network environment for efficient delivery of Broadcast, Unknown-unicast and Multicast (BUM) traffic while eliminating the need for maintaining a huge amount of multicast state in the underlay. This document describes BGP extensions for advertising the BIER-specific information. These extensions are applicable in those multi-tenant data centers where BGP instead of IGP is deployed as an underlay for network reachability advertisement. These extensions may also be applicable in other scenarios. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bier-idr-extensions/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-bier-idr-extensions-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-idr-extensions-02 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Jan 18 08:26:56 2017 Return-Path: X-Original-To: bier@ietf.org Delivered-To: bier@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F2166129456; Wed, 18 Jan 2017 08:26:50 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.40.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148475681094.2189.3965752492392091657.idtracker@ietfa.amsl.com> Date: Wed, 18 Jan 2017 08:26:50 -0800 Archived-At: Cc: bier@ietf.org Subject: [Bier] I-D Action: draft-ietf-bier-bgp-ls-bier-ext-00.txt X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2017 16:26:51 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Bit Indexed Explicit Replication of the IETF. Title : BGP Link-State extensions for BIER Authors : Ran Chen Zheng Zhang Vengada Prasad Govindan IJsbrand Wijnands Filename : draft-ietf-bier-bgp-ls-bier-ext-00.txt Pages : 8 Date : 2017-01-10 Abstract: Bit Index Explicit Replication (BIER) is an architecture that provides optimal multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain any multicast related per- flow state. BIER also does not require any explicit tree-building protocol for its operation. A multicast data packet enters a BIER domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs). The BFIR router adds a BIER header to the packet. The BIER header contains a bitstring in which each bit represents exactly one BFER to forward the packet to. The set of BFERs to which the multicast packet needs to be forwarded is expressed by setting the bits that correspond to those routers in the BIER header. This document specifies extensions to the BGP Link-state address- family in order to advertising BIER information. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bier-bgp-ls-bier-ext/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-bier-bgp-ls-bier-ext-00 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sat Jan 21 23:31:33 2017 Return-Path: X-Original-To: bier@ietf.org Delivered-To: bier@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EB75C1294F7; Sat, 21 Jan 2017 23:31:27 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.40.4 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148507028795.32281.5828979745249946310.idtracker@ietfa.amsl.com> Date: Sat, 21 Jan 2017 23:31:27 -0800 Archived-At: Cc: bier@ietf.org Subject: [Bier] I-D Action: draft-ietf-bier-bier-yang-01.txt X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jan 2017 07:31:28 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Bit Indexed Explicit Replication of the IETF. Title : YANG Data Model for BIER Protocol Authors : Ran Chen Fangwei Hu Zheng Zhang Xianxian Dai Mahesh Sivakumar Filename : draft-ietf-bier-bier-yang-01.txt Pages : 19 Date : 2017-01-21 Abstract: This document defines a YANG data model for BIER configuration and operation. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bier-bier-yang/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-bier-bier-yang-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-bier-yang-01 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Jan 24 08:29:31 2017 Return-Path: X-Original-To: bier@ietf.org Delivered-To: bier@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FE2112961D; Tue, 24 Jan 2017 08:29:29 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.40.4 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148527536923.12634.4323331323505322789.idtracker@ietfa.amsl.com> Date: Tue, 24 Jan 2017 08:29:29 -0800 Archived-At: Cc: bier@ietf.org Subject: [Bier] I-D Action: draft-ietf-bier-pmmm-oam-01.txt X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.17 List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2017 16:29:29 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Bit Indexed Explicit Replication of the IETF. Title : Performance Measurement (PM) with Marking Method in Bit Index Explicit Replication (BIER) Layer Authors : Greg Mirsky Lianshu Zheng Mach Chen Giuseppe Fioccola Filename : draft-ietf-bier-pmmm-oam-01.txt Pages : 7 Date : 2017-01-23 Abstract: This document describes a passive performance measurement method for multicast service over Bit Index Explicit Replication (BIER) domain. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bier-pmmm-oam/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-bier-pmmm-oam-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-pmmm-oam-01 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/