Mirja, 

See inline. 

On 9/25/18, 6:29 PM, "netmod on behalf of Mirja Kuehlewind (IETF)" 
<[email protected] on behalf of [email protected]> wrote:

    Hi Mahesh, hi Eliot,
    
    please see below.
    
    > Am 25.09.2018 um 22:25 schrieb Eliot Lear <[email protected]>:
    > 
    > Just on this point:
    > 
    > On 25.09.18 20:35, Mahesh Jethanandani wrote:
    >>> That’s do bad. However, the document must at least say that it’s scope 
is
    
    (sorry for the type… I meant to say „too bad“.)
    
    >>> restricted to TCP and UDP only and it would also be nice to reason why 
that restriction is and what would need to be done to extend it in future.
    >> 
    >> To the contrary. The model is not restricted to TCP and UDP. In Section 
2, the document states that:
    >> 
    >>    ACL implementations in every device may vary greatly in terms of the
    >>    filter constructs and actions that they support.  Therefore this
    >>    draft proposes a model that can be augmented by standard extensions
    >>    and vendor proprietary models.
    >> 
    >> 
    Yes, ACL implementations differ, however, the protocol spec for SCTP and 
DCCP don’t have different implementation; their are mostly fixed. 
Unfortunately, firewalls often just block any other traffic than TCP and UDP, 
and restricting such a model only to those protocols will definitely not help 
the situation.
    
    >> 
    >> It is a different matter that it has chosen not to support SCTP and 
DCCP. That is because implementations today have not felt the market need to 
add support for those protocols. But that does not prevent anyone from adding 
support for them.
    
    If your YANG model does not support long-existent and well-specified 
protocols, that doesn’t make it any easier to add support for these protocols 
to your firewall.
    
    >> 
    >> As far as an example for how the model can be extended in the future, 
see Appendix A - Extending ACL model examples.
    > 
    > It's important to not try to boil the ocean, and this model is already 
boiling a rather large river.  There's room for someone else to do more work.  
I know I did ;-)
    
    I would think that adding another well-specified protocols is actually only 
a limited effort.

How many YANG models have you authored? This would be a great opportunity. 

   However, I don’t want to enforce a lot of additional work if people are not 
interested in that. What I still would like to see in the document is to make 
clear that these protocols have not just been    not considered but some 
reasoning why only the currently supported protocols have been selected (in 
order to make the reader aware that this is not a full set).

I would think pointing out that these protocols are out of scope would suffice. 
However, I'll leave that to the author.

Thanks,
Acee

    
    Mirja
    
    
    > 
    > Eliot
    
    _______________________________________________
    netmod mailing list
    [email protected]
    https://www.ietf.org/mailman/listinfo/netmod
    

_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to