@@ -131,20 +131,27 @@ module ietf-acl-enh {
131131 identity layer4 {
132132 base offset-type;
133133 description
134- "The offset start right after the IP header. This can be
135- typically the beginning of transport header (e.g., TCP
136- or UDP) or any encapsulation scheme over IP such as
137- IP-in-IP." ;
134+ "The offset starts right after the IP header (including
135+ any options or headers pertaining to that IP layer, e.g.,
136+ IPv6 Extension Headers and the Authentication Header (AH)).
137+
138+ This can be typically the beginning of transport header
139+ (e.g., UDP, TCP, SCTP, and DCCP) or any encapsulation
140+ scheme over IP such as IP-in-IP." ;
138141 }
139142
140143 identity payload {
141144 base offset-type;
142145 description
143- "The offset start right after the end of the transport
144- payload . For example, this represents the beginning of the
146+ "The offset starts right after the end of the transport
147+ header . For example, this represents the beginning of the
145148 TCP data right after any TCP options or the beginning of
146- the UDP payload right after the UDP header." ;
147- }
149+ the UDP payload right after the UDP header.
150+
151+ This type may be used for matches against any data in
152+ the transport payload and/or any surplus area (if any,
153+ such as in UDP)." ;
154+ }
148155
149156 identity tcp-flag {
150157 description
@@ -437,7 +444,7 @@ module ietf-acl-enh {
437444 leaf type {
438445 type fragment-type;
439446 description
440- "What fragment type to look for." ;
447+ "Specifies what fragment type to look for." ;
441448 }
442449 }
443450
@@ -519,7 +526,7 @@ module ietf-acl-enh {
519526 type operator;
520527 default "match" ;
521528 description
522- "How to interpret the prefix match." ;
529+ "How to interpret the pattern match." ;
523530 }
524531 leaf pattern {
525532 type binary ;
0 commit comments