[MBONED] Kathleen Moriarty's Discuss on draft-ietf-mboned-interdomain-peering-bcp-11: (with DISCUSS and COMMENT)

[Kathleen Moriarty <[e-mail]>]

Kathleen Moriarty has entered the following ballot position for
draft-ietf-mboned-interdomain-peering-bcp-11: Discuss

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.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mboned-interdomain-peering-bcp/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thanks for your work on this draft.  I'd like to see some text clarifications
on security recommendations that should not be difficult to resolve.

Section 4.4 - the exchange of supporting information could be sensitive, are
there security requirements on the exchange?  I don’t see them in this section.

Section 6 - For the following text, it would be helpful to see some
recommendations:
   “DRM and Application Accounting, Authorization and Authentication
   should be the responsibility of the multicast application source
   provider and/or AD-1. AD-1 needs to work out the appropriate
   agreements with the source provider.”


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I agree with and support Alissa's Discuss and comments.  Since she already
holds a discuss on this point, here are my comments: Section 4.3.3 clearly
refers to different types of logs, some have well known methods of delivery
(syslog) and authentication, but setting a minimum requirement for secure
exchange including encryption and authentication should be included in this
section. The protocols and options may vary between the log types.