Re: [Bier] Deborah Brungard's Block on charter-ietf-bier-01-06: (with BLOCK)

Hi Deborah,

Sure - that may end up making Toerless split his draft, but if TEAS is
interested
and willing, that's fine.

I don't know if it's so much traffic-engineering as
centralized/controller-based, but
that falls closer to TEAS or PCE anyway.

I'll update the charter and send you a ping.

Thanks,
Alia

On Thu, Feb 22, 2018 at 7:20 PM, BRUNGARD, DEBORAH A <db3546@att.com> wrote:

> Hi Alia,
>
>
>
> This looks good- just slight tweak:
>
>  * teas on control-plane mechnisms to use BIER-TE forwarding mechanisms.
>
> /s/
>
>  * teas on architecture and control-plane mechanisms to use BIER-TE
> forwarding mechanisms.
>
>
>
> Thanks-
>
> Deborah
>
>
>
>
>
>
>
> *From:* Alia Atlas [mailto:akatlas@gmail.com]
> *Sent:* Thursday, February 22, 2018 2:54 PM
> *To:* BRUNGARD, DEBORAH A <db3546@att.com>; Toerless Eckert <tte@cs.fau.de
> >
> *Cc:* The IESG <iesg@ietf.org>; BIER WG <bier@ietf.org>;
> bier-chairs@ietf.org
> *Subject:* Re: [Bier] Deborah Brungard's Block on
> charter-ietf-bier-01-06: (with BLOCK)
>
>
>
> Hi Deborah,
>
>
>
> How about instead of:
>
>
>
> OLD
>
>   8) BIER Traffic Engineering: Definition of an architecture, and
>
>        specification of the associated technology, for a BIER-based
>
>        mechanism to support traffic engineering."
>
>
>
> NEW
>
>   9) Forwarding Plane Mechanisms for BIER Traffic Engineering: definition
> of
>
>       how the new BIER forwarding plane structures (e.g. BIFT) can be used
> to
>
>       support engineered multicast trees.  No control-plane work will be
> done in BIER-WG.
>
>
>
> and the WGs to coordinate with will have added:
>
>
>
>  * teas on control-plane mechnisms to use BIER-TE forwarding mechanisms.
>
>
>
> Regards,
>
> Alia
>
>
>
> On Wed, Feb 21, 2018 at 8:08 PM, Deborah Brungard <db3546@att.com> wrote:
>
> Deborah Brungard has entered the following ballot position for
> charter-ietf-bier-01-06: Block
>
> 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.)
>
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/charter-ietf-bier/
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_charter-2Dietf-2Dbier_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6UhGpW9lwi9dM7jYlxXD8w&m=SooQxG2cIgm-ictCU8wcQwGTx3k2rpMjyGxaHo_1c8Q&s=kSYF29AsPrYX28KSEy12rHimJJC6ACzJyRTtMzjdEs4&e=>
>
>
>
> ----------------------------------------------------------------------
> BLOCK:
> ----------------------------------------------------------------------
>
> While a Discuss, this should be simple to address as I think it's a bit of
> a misnomer
> which Alvaro has already noted.
> About:
> "8) BIER Traffic Engineering: Definition of an architecture, and
>    specification of the associated technology, for a BIER-based
>    mechanism to support traffic engineering."
>
> Looking at the wg draft (which it seems this new charter item is based on),
> the draft says:
> "It does support traffic engineering by explicit hop-by-hop forwarding"
> and "it is more similar to SR than RSVP-TE".
>
> So it is not TE, it is explicit forwarding. As Alvaro noted, this should
> not
> be identified in the charter as TE. I don't see any need for this new item
> to
> be in the charter (as Alvaro noted).
>
> This is a Discuss because if this is not a simple misnomer, then this work
> clashes with TEAS. TEAS is chartered and responsible for
> "Traffic-engineering
> architectures for generic applicability across packet and non-packet
> networks.
> This includes both networks that include the use of PCE and those that do
> not."
>
>
>
>
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bier&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=6UhGpW9lwi9dM7jYlxXD8w&m=SooQxG2cIgm-ictCU8wcQwGTx3k2rpMjyGxaHo_1c8Q&s=MB4vhOEnedbfqsLsX6vVSCxkIAXrFHi-fF-mYJyT4ZU&e=>
>
>
>