Hi
I support publication of this document, but there are a few minor
editorial issues that needs to be addressed.
Section 2.1 has minor issues:
For comparison, another method of supporting customer ASM is
generally referred to "rpt-spt" mode. Section "13. Switching from a
^^^^
referred to as
Shared C-Tree to a Source C-Tree" of [RFC6514] specifies the MVPN SA
procedures for that mode, but those SA routes are replacement for
^^^
are a replacement
PIM-ASM assert and (s,g,rpt) prune mechanisms, not for source
discovery purpose. MVPN/MSDP SA interoperation for the "rpt-spt"
^^^^^^^^^
purposes?
mode is outside of the scope of this document. In the rest of the
document, the "spt-only" mode is assumed.
In section 3:
of the document, it is referred to as the PE mesh group. It MUST not
^^^^^^^^^^
This is not allowed, should be "MUST NOT".
In section 3:
In addition to procedures in [RFC6514], an MVPN PE may be provisioned
to generate MSDP SA messages from received MVPN SA routes, with or
without fine policy control. If a received MVPN SA route is to
I'm not sure what is meant by "fine policy control" here. Is that one
may have policy for specific SAs? Should it be "fine grained"?
Section 5:
"IANA Assignment" should be "IANA Considerations".
Regards,
Stig
On Tue, Sep 10, 2019 at 7:26 AM Bocci, Matthew (Nokia - GB)
<matthew.bo...@nokia.com> wrote:
>
> Hello Working Group,
>
>
>
> This email starts a two week Working Group Last Call on
> draft-ietf-bess-mvpn-msdp-sa-interoperation-03 [1].
>
>
>
> This poll runs until 25 September 2019.
>
>
>
> We are also polling for knowledge of any undisclosed IPR that applies to this
> Document, to ensure that IPR has been disclosed in compliance with IETF IPR
> rules (see RFCs 3979, 4879, 3669 and 5378 for more details).
>
>
>
> If you are listed as an Author or a Contributor of this document please
> respond to this email and indicate whether or not you are aware of any
> relevant undisclosed IPR. The Document won't progress without answers from
> all the Authors and Contributors.
>
>
>
> There are currently no IPR disclosures against the document.
>
>
>
> If you are not listed as an Author or a Contributor, then please explicitly
> respond only if you are aware of any IPR that has not yet been disclosed in
> conformance with IETF rules.
>
>
>
> We are also polling for any existing implementation as per [2].
>
>
>
> Thank you,
>
> Matthew and Stephane
>
>
>
> [1]
> https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-msdp-sa-interoperation/
>
> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>
>
>
>
>
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess
_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
