Stephane Litkowski has requested publication of draft-ietf-bess-evpn-mh-pa-10
as Proposed Standard on behalf of the BESS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-mh-pa/
___
BESS
Hi,
Here is my last review (as WG chair) of the draft, I have also requested a
GEN-ART review.
Abstract:
Use "RFC7432" as a plain text reference and not as a link (xml xtarget) in the
abstract.
Introduction:
s/QOS/QoS/
I think this sentence is useless in the text as previous one already
Stephane Litkowski has requested publication of
draft-ietf-bess-evpn-irb-extended-mobility-17 as Proposed Standard on behalf of
the BESS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-irb-extended-mobility
HI Neeraj,
Many thanks for the updates, the text is more clear now.
I’ll do the write up and proceed.
Stephane
From: Neeraj Malhotra (nmalhotr)
Sent: Monday, October 16, 2023 11:31 PM
To: slitkows.i...@gmail.com; Stephane Litkowski (slitkows)
; draft-ietf-bess-evpn-irb-extended-mobil
Hi Authors,
Please find below my review of the latest version of the draft:
Abstract:
The abstract refers to RFC7432bis but don’t make RFC7432bis as normative
reference and also drafts is marked as updating RFC7432.
Here you should make a choice, either you base the draft on RFC7432 and not
Hi folks,
We are missing the IPR reply from Samir to close the WG adoption.
Thanks,
Stephane
From: BESS mailto:bess-boun...@ietf.org>> on behalf of
Stephane Litkowski (slitkows)
mailto:slitkows=40cisco@dmarc.ietf.org>>
Date: Monday, October 10, 2022 at 1:40 AM
To: bess-cha
Hello,
This email begins a two-weeks WG adoption poll for
draft-sajassi-bess-evpn-ac-aware-bundling-06 [1].
Please review the draft and post any comments to the BESS working group list.
We are also polling for knowledge of any undisclosed IPR that applies to this
document, to ensure that IPR
Hi WG,
Authors of RFC7432bis
(https://datatracker.ietf.org/doc/draft-ietf-bess-rfc7432bis/) would like to
request early allocation of code point for F-flag:
This document requests allocation of bit 3 in the "EVPN Layer 2
Attributes Control Flags" registry with name F:
F Flow
Stephane Litkowski has requested publication of
draft-ietf-bess-evpn-vpws-fxc-07 as Proposed Standard on behalf of the BESS
working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-vpws-fxc
Stephane Litkowski has requested publication of draft-ietf-bess-evpn-pref-df-08
as Proposed Standard on behalf of the BESS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-pref-df/
___
BESS
Stephane Litkowski has requested publication of
draft-ietf-bess-evpn-virtual-eth-segment-07 as Proposed Standard on behalf of
the BESS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-virtual-eth-segment
Stephane Litkowski has requested publication of
draft-ietf-bess-evpn-igmp-mld-proxy-09 as Proposed Standard on behalf of the
BESS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-igmp-mld-proxy
Stephane Litkowski has requested publication of
draft-ietf-bess-mvpn-evpn-aggregation-label-06 as Proposed Standard on behalf
of the BESS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-evpn-aggregation-label
Hi,
Here is my review of the document:
Section 2.2:
s/the DCB MUST not intersect/the DCB MUST NOT intersect/
I don't fully understand the purpose of the second part of the sentence :
"or those routers MUST be
considered as part of the "domain"."
I think the DCB must not intersect with any
Hi authors,
I have completed my shepherd's write up of the document.
However, there is a normative reference to vES draft which we haven't closed
yet. I'll hold on the doc, until we have moved forward vES. It should be closed
soon I think. We'll send both together to IESG.
Thanks for your
Date: Monday, January 4, 2021 at 4:14 AM
To: Rabadan, Jorge (Nokia - US/Mountain View) ,
'Stephane Litkowski (slitkows)' ,
draft-ietf-bess-evpn-ipvpn-interwork...@ietf.org
Cc: bess@ietf.org , bess-cha...@ietf.org
Subject: RE: draft-ietf-bess-evpn-ipvpn-interworking chair review
Hi Jorge,
Hi Authors,
Please find below my chair review related to
draft-ietf-bess-evpn-ipvpn-interworking.
BTW, you need to refresh the draft now, it has expired.
Section 3:
* Nit:
s/uniqueness of the DOMAIN- ID/uniqueness of the DOMAIN-ID/
* a) I agree with DJ's comment on: "This attribute
Thanks,
I have fixed all what was mentioned below for the next revision.
Stephane
-Original Message-
From: Acee Lindem (acee)
Sent: lundi 17 août 2020 13:46
To: Erik Kline ; The IESG
Cc: matthew.bo...@nokia.com; bess-cha...@ietf.org; bess@ietf.org;
Hi Authors,
Please find my review of the document.
Nits to be fixed:
https://www6.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-ietf-bess-evpn-unequal-lb-03.txt
Section 1.1:
* s/it MUST add a link to both PE1/it must add a link to both PE1/ => this
is not a normative
Stephane Litkowski has requested publication of
draft-ietf-bess-evpn-bum-procedure-updates-08 as Proposed Standard on behalf of
the BESS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-bum-procedure-updates
Stephane Litkowski has requested publication of
draft-ietf-bess-mvpn-fast-failover-10 as Proposed Standard on behalf of the
BESS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-fast-failover
Hi,
Following our fruitful discussion during BESS meeting yesterday, I have
published a draft to revise RFC5549.
Brgds,
Stephane
-Original Message-
From: internet-dra...@ietf.org
Sent: mercredi 20 novembre 2019 13:39
To: Swadesh Agrawal ; Stephane Litkowski (slitkows)
; Krishna
Hi,
This email begins a two-weeks WG adoption poll for
draft-snr-bess-pbb-evpn-isid-cmacflush [1]
Please review the draft and post any comments to the BESS working group
list.
We are also polling for knowledge of any undisclosed IPR that applies to
this Document, to ensure that IPR has been
Stephane Litkowski has requested publication of
draft-ietf-bess-nsh-bgp-control-plane-12 as Proposed Standard on behalf of the
BESS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane
Hi,
This email begins a two-weeks WG adoption poll
for draft-rabadan-bess-vendor-evpn-route-07 [1]
Please review the draft and post any comments to the BESS working group
list.
We are also polling for knowledge of any undisclosed IPR that applies to
this Document, to ensure that IPR has been
Stephane Litkowski has requested publication of
draft-ietf-bess-evpn-inter-subnet-forwarding-08 as Proposed Standard on behalf
of the BESS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-inter-subnet-forwarding
Stephane Litkowski has requested publication of
draft-ietf-bess-bgp-vpls-control-flags-06 as Proposed Standard on behalf of the
BESS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-bgp-vpls-control-flags
Stephane Litkowski has requested publication of draft-ietf-bess-mvpn-mib-09 as
Proposed Standard on behalf of the BESS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-mib/
___
BESS mailing
Stephane Litkowski has requested publication of
draft-ietf-bess-l2l3-vpn-mcast-mib-14 as Proposed Standard on behalf of the
BESS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-l2l3-vpn-mcast-mib
Stephane Litkowski has requested publication of
draft-ietf-bess-mvpn-expl-track-09 as Proposed Standard on behalf of the BESS
working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-expl-track
30 matches
Mail list logo
