Re: [MEXT] implications for draft-tsirtsis-mext-binary-filters-00.txt

[Hesham Soliman <hesham at elevatemobile.com>]

> One more comments about the draft:
> 
>    (G)Source Port - Low
> 
>       This field identifies the lowest source port number within a range
>       of port numbers that will be used in data packets, as seen by the
>       home agent.
> 
>    (H)Source Port - High
> 
>       This field identifies the highest source port number within a
>       range of port numbers that will be used in data packets, as seen
>       by the home agent.  If a single port is indicated then this field
>       SHOULD NOT be included.  If it is included it SHOULD be set to the
>       value of the Source Port - Low field.
> 
>    (I)Destination Port - Low
> 
>       This field identifies the lowest destination port number within a
>       range of port numbers that will be used in data packets as seen by
>       the home agent.
> 
> 
>    (K)Destination Port - High
> 
>       This field identifies the highest destination port number within a
>       range of port numbers that will be used in data packets as seen by
>       the home agent.  If a single port is indicated then this field
>       SHOULD NOT be included.  If it is included it SHOULD be set to the
>       value of the Dst Port - Low field.
> 
> 
> question: all these options can be present only if the (B)Protocol
> option is present, correct?

=> I don't see why. You should be able to specify port that span transport
protocols if you want. Of course, in practice all the well-known ports are
allocated to both TCP and UDP anyway.

Hesham

> 
> 
> _______________________________________________
> MEXT mailing list
> MEXT at ietf.org
> https://www.ietf.org/mailman/listinfo/mext