[NSIS] Again: NATFW TRACE semantics

Hi all,

The semantics of TRACE in the NATFW NSLP is still unclear, i.e., only  
partially specified.

I have already asked for some input on this on May 11th (see attached  
email) and highlighted the issue in the issue tracker (no. 77) and  
during the last NSIS session at the 66th IETF meeting in Montreal.  
See links below as reference.

There has still been no input on this and would follow the suggestion  
made on slide no. 10 of the IETF-66 presentation:

Remove TRACE completely.

Please respond by October 11th, 11pm Pacific Time, if have semantics  
for TRACE.
If there is no proposal for TRACE semantics, I will remove TRACE  
completely.

Thanks

   Martin

https://kobe.netlab.nec.de/roundup/nsis-natfw-nslp/issue77
http://www3.ietf.org/proceedings/06jul/slides/nsis-16/sld9.htm
http://www3.ietf.org/proceedings/06jul/slides/nsis-16/sld10.htm

Am 11.05.2006 um 15:07 schrieb Martin Stiemerling:

> Dear all,
>
> This is a request to read about the TRACE message in
> the NATFW NSLP draft
> (http://www.ietf.org/internet-drafts/draft-ietf-nsis-nslp- 
> natfw-11.txt)
> and to comment on it. The semantics of TRACE is preliminary
> and we need to get more input on it what exactly TRACE should
> do in the opinion of the working group.
>
> The important section about TRACE are:
> - 3.8.6
> - 4.2.8
> - 4.3.5
>
> Currently, TRACE can be only sent by the session owner. TRACE
> will collect the identifiers of the NATFW NSLP nodes involved
> in a particular session. However, it is not specified which identifier
> in a case of a NAT is included or what happens if there is a change
> of the address family (e.g. from IPv4 to IPv6) is happening.
>
> Looking forward to the proposals and discussions
>
>    Martin
>
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis