[manet] Gorry Fairhurst's Discuss on draft-ietf-manet-dlep-c redit-flow-control-18: (with DISCUSS and COMMENT)

Gorry Fairhurst via Datatracker <[email protected]>
Newsgroups gmane.ietf.manet
Message-ID <174284288867.1583733.12577047885425335668@dt-datatracker-5b9b68c5b6-zxk6z>
Gorry Fairhurst has entered the following ballot position for
draft-ietf-manet-dlep-credit-flow-control-18: 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/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-credit-flow-control/



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

I was unaware of this work in Manet, and thank you for making an interesting
and useful specification. I have two concerns I’d like to discuss:

1. The text says: “In the absence of a wildcard, a packet may not match any of
the data items and, in this case, SHOULD be dropped by the router.”.- Why is
this not a MUST? (If it needs to be a SHOULD, then please add text to explain
what happens whene there is no match and explain whether sending this pacekt
also consumens credit.)

2. If a packet is not matched and is dropped, ought it to be logged? (It would
be logged if there was no FID). Either way, the specification ought to explain
whether an entry in the log is to be expected.


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

I don’t think the security mechanisms are sufficiently defined to be useful.
Please can you explain what threats these updates are expected to counter. This
currently leads to two very ineffective security considerations:



_______________________________________________
manet mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.