NATFW issue: proxy flag handling

[writing with chair's hat off, i.e., as NATFW NSLP author only!]

Hi all,

Section 4.1.  "NSLP Header" also defines some processing for the  
proxy (p) flag and the different messages.
The text:
The P flag indicates the usage of proxy mode.  If proxy mode is used
it MUST be set to 1.  Proxy mode usage is only allowed in combination
with the message types CREATE and EXTERNAL, P=1 MUST NOT be set with
message types other than CREATE and EXTERNAL.  The P flag MUST be
ignored when processing messages with type RESPONSE.  An error
RESPONSE message of class 'Protocol error' (0x3) and type 'Bad flags
value' (0x03) MUST be generated, if the P flag is set in NOTIFY
messages.

It's strange that the P flag must be ignored for RESPONSE but  
generates an error for NOTIFY.


Change proposal:
OLD:
The P flag MUST be ignored when processing messages with type  
RESPONSE.  An error RESPONSE message of class 'Protocol error' (0x3)  
and type 'Bad flags value' (0x03) MUST be generated, if the P flag is  
set in NOTIFY

NEW:
The P flag MUST be ignored when processing messages with type  
RESPONSE and NOTIFY.



The P flag is anyhow meaningless with those two message types.

  Martin


[email protected]

NEC Laboratories Europe - Network Research Division

NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road,  
London W3 6BL | Registered in England 2832014

_______________________________________________
nsis mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/nsis