From nsis-bounces@ietf.org Tue Jan 08 09:05:59 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCF5Y-000114-R5; Tue, 08 Jan 2008 09:05:56 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JCF5W-00010n-PT
	for nsis-confirm+ok@megatron.ietf.org; Tue, 08 Jan 2008 09:05:54 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCF5U-00010R-Ka
	for nsis@ietf.org; Tue, 08 Jan 2008 09:05:52 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCF5U-0004MG-8L
	for nsis@ietf.org; Tue, 08 Jan 2008 09:05:52 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 78E5228000357
	for <nsis@ietf.org>; Tue,  8 Jan 2008 15:05:51 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id T9kkFijbLhHG for <nsis@ietf.org>;
	Tue,  8 Jan 2008 15:05:51 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 685CB28000355
	for <nsis@ietf.org>; Tue,  8 Jan 2008 15:05:46 +0100 (CET)
Received: from [10.1.1.109] ([10.1.1.109]) by mx1.office over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 8 Jan 2008 15:05:46 +0100
Mime-Version: 1.0 (Apple Message framework v753)
Content-Transfer-Encoding: 7bit
Message-Id: <15C5FC3D-A4C5-4243-89F5-4B3D64BD4413@netlab.nec.de>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: nsis <nsis@ietf.org>
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Date: Tue, 8 Jan 2008 15:05:44 +0100
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 08 Jan 2008 14:05:46.0314 (UTC)
	FILETIME=[908402A0:01C851FF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: [NSIS] Available NSIS Implementations as of Jan 2008
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org

[This mail has been sent to the NSIS list, nsis-imp@ietf, and nsis- 
imp@goettingen.
Sorry for any duplicates you may receive]


Dear all,

I'm preparing a web page with a list of all available NSIS GIST, QoS  
NSLP, and NATFW NSLP implementations.

Please send the following information to nsis-chairs@tools.ietf.org  
if you have a implementation or multiple implementations of GIST, QoS  
or NATFW NSLP, or any other NSIS component:

- Name of release
- What (GIST, QoS NSLP, NATFW NSLP)
- based on which draft version
- (if possible) feature set (e.g. full QoS NSLP implementation, GIST  
but only D-MODE, etc)
- available for which operating system (e.g., Linux, FreeBSD,  
Windows, OpenWRT, etc)
- License (e.g. closed source, GPL, etc)
- Link to software or web page
- Implementation tested at interop?
- Contact e-mail address

Thanks in advance

   Martin

stiemerling@netlab.nec.de

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
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Tue Jan 08 09:54:06 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCFq9-00013L-HK; Tue, 08 Jan 2008 09:54:05 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JCFq8-00013G-52
	for nsis-confirm+ok@megatron.ietf.org; Tue, 08 Jan 2008 09:54:04 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCFq7-00011b-O5
	for nsis@ietf.org; Tue, 08 Jan 2008 09:54:03 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCFq5-0005Ob-WF
	for nsis@ietf.org; Tue, 08 Jan 2008 09:54:03 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 85A592800035C
	for <nsis@ietf.org>; Tue,  8 Jan 2008 15:54:01 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cKJK4R3WBMqr for <nsis@ietf.org>;
	Tue,  8 Jan 2008 15:54:01 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 6044828000357
	for <nsis@ietf.org>; Tue,  8 Jan 2008 15:53:56 +0100 (CET)
Received: from [10.1.1.109] ([10.1.1.109]) by mx1.office over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 8 Jan 2008 15:53:56 +0100
Mime-Version: 1.0 (Apple Message framework v753)
To: nsis <nsis@ietf.org>
Message-Id: <C7D86860-A84B-4F94-84C2-FD73665A44D9@netlab.nec.de>
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Date: Tue, 8 Jan 2008 15:53:54 +0100
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 08 Jan 2008 14:53:56.0254 (UTC)
	FILETIME=[4B0DDBE0:01C85206]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9c7d7a899dc8f3389bf7ace6f0ad8e29
Subject: [NSIS] Review of draft-ietf-nsis-qos-nslp-15.txt
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1168222975=="
Errors-To: nsis-bounces@ietf.org


--===============1168222975==
Content-Type: multipart/alternative; boundary=Apple-Mail-7-306019039


--Apple-Mail-7-306019039
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hi all,

Here is my chair's review of draft-ietf-nsis-qos-nslp-15.txt.

I have reviewed the whole draft and do not see any issue with it. It  
is written in an excellent way and seems to be just fine. Thanks to  
all who contributed and especially to the editors.

The comments are just editorial or minor clarifications. Please fix  
them if possible and submit a new version.

Editorial issues:

- ID nits throws some output (see attached at bottom of this mail).  
The only relevant is an editorial nit; 2nd under "miscellaneous  
warnings".

- page 6, definition of session: " A session defines an association  
between a QNI and QNR related to a data flow." Just for my  
understanding: This sounds such as the involved QNEs on the path are  
not part of the session? The definition is a bit unclear in this  
respect, IMHO.

- page 9, first para has some strange line break, between  
"...network" and "management..."

- page 9: para starting with "Policy control..." refers to qos-auth  
which is a I-D. Do we still need to point to this draft and if yes,  
why it is happening here in the introduction and not in the  
appropriate section?

- page 11, first para (cont'd from previous page): s/source of the  
each/source of each

- page 11, section 3.1.2, third para, refers to the QSPEC as "ongoing  
effort" which is hopefully not true anymore. Rephrasing would be good.

- page 12, the para before the last para, "QoS models..." again  
refers to the QSPEC draft, seems to superfluous in this section.

- page 14, third para refers to nslp-auth draft. As we won't have  
this draft as WG item, it is appropriate to remove the reference here  
and also from  the reference section

- page 16, last para, s/a unidirectional/an unidirectional

- page 20, the para before the last para refers to "middle of  
session". What is "middle of session"?

- page 21, para before section 3.2.12.1 seems to belong in section  
3.2.12.1

- page 24, section 3.2.12 it would be nice to refer to 5.2.5.2 here,  
so that people can jump there to see the solution, if desired, and  
the more exhaustive explanation

- page 34, last para of section 4.5 has a self-reference to section  
4.5 but claiming that it is different.

- page 42, middle of page says three flags, but there are four of them.

- page 45, second para says "Retransmissions SHOULD be disabled." If  
haven't understood on which level the retransmission should be  
disabled (GIST or NSLP level?).

- page 70, section 5.3.7, first para, last sentence: at locationg i  
refer. Needs to be fixed somehow.

- page 74, section 5.4.1, list end of the page: s/The SCOPING/the  
SCOPING. also for following bullets. Also for the list on  page 75.

- Section 5.4.1 and 5.4.2 say
..."monitored.   If they differ then the BREAK flag of new generated  
messages (e.g.,  QUERY, RESERVE or RESPONSE) SHOULD be set.  In  
situations ..."
Would RECOMMENDED be more appropriate here? (of course considering  
also the case described after ("...BREAK flag MUST not be set...").

- page 76, last para: "Note that QUERY messages with the RESERVE-INIT  
flag set MUST be answered by the QNI." Shouldn't it read "...answered  
by the QNR."?

- page 79, section 6 (but not going in 6.1 and subsequent): The lists  
are broken (formatting issue)

- page 90: Appendix A. It would be good to add something along "This  
appendix is informational only."

- page 95: Heading has two times "Appendix B".


That's it.

Thanks!

   Martin

*********
ID  Nits:

idnits 2.05.03

tmp/draft-ietf-nsis-qos-nslp-15.txt:

   Checking boilerplate required by RFC 3978 and 3979, updated by RFC  
4748:
    
------------------------------------------------------------------------ 
----

      No issues found here.

   Checking nits according to http://www.ietf.org/ietf/1id- 
guidelines.txt:
    
------------------------------------------------------------------------ 
----

      No issues found here.

   Checking nits according to http://www.ietf.org/ID-Checklist.html:
    
------------------------------------------------------------------------ 
----

      No issues found here.

   Miscellaneous warnings:
    
------------------------------------------------------------------------ 
----

   == The copyright year in the IETF Trust Copyright Line does not  
match the
      current year

   == Using lowercase 'not' together with uppercase 'MUST' is not an  
accepted
      usage according to RFC 2119.  Please use 'MUST NOT' (if that is  
what you
      mean).

      Found 'MUST not' in this paragraph:

      If a stateful QoS NSLP QNE receives a QUERY message with the
      RESERVE-INIT flag and BREAK flag set then the BREAK flag of new  
generated
      messages (e.g., QUERY, RESERVE or RESPONSE) MUST be set.  When  
a stateful
      QoS NSLP QNE receives a QUERY message with the the RESERVE-INIT  
flag set
      and BREAK flag not set then then the IP-TTL and Original-TTL  
values in
      GIST RecvMessage primitive MUST be monitored. If they differ  
then the
      BREAK flag of new generated messages (e.g., QUERY, RESERVE or  
RESPONSE)
      SHOULD be set.  In situations where a QNE or a domain is able  
to provide
      QoS using other means, see Section 3.3.5, then the BREAK flag  
MUST not be
      set.


   Checking references for intended status: Proposed Standard
    
------------------------------------------------------------------------ 
----

      (See RFC 3967 for information about using normative references to
      lower-maturity documents in RFCs)

   == Outdated reference: A later version (-18) exists of
      draft-ietf-nsis-qspec-17

   == Outdated reference: A later version (-08) exists of
      draft-ietf-nsis-applicability-mobility-signaling-07

   == Outdated reference: A later version (-12) exists of
      draft-ietf-nsis-rmd-10


      Summary: 0 errors (**), 5 warnings (==), 0 comments (--).
------------------------------------------------------------------------ 
--------

stiemerling@netlab.nec.de

NEC Laboratories Europe - Network Research Division

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


--Apple-Mail-7-306019039
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
Hi all,<div><br class=3D"webkit-block-placeholder"></div><div>Here is my =
chair's review of=A0draft-ietf-nsis-qos-nslp-15.txt.=A0</div><div><br =
class=3D"webkit-block-placeholder"></div><div>I have reviewed the whole =
draft and do not see any issue with it. It is written in an excellent =
way and seems to be just fine. Thanks to all who contributed and =
especially to the editors.=A0</div><div><br =
class=3D"webkit-block-placeholder"></div><div>The comments are just =
editorial or minor clarifications. Please fix them if possible and =
submit a new version.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Editorial =
issues:</div><div><br class=3D"webkit-block-placeholder"></div><div>- ID =
nits throws some output (see attached at bottom of this mail). The only =
relevant is an editorial nit; 2nd under "miscellaneous =
warnings".=A0</div><div><br =
class=3D"webkit-block-placeholder"></div><div>- page 6, definition of =
session: "=A0A session defines an association between a QNI and =
QNR=A0related to a data flow." Just for my understanding: This sounds =
such as the involved QNEs on the path are not part of the session? The =
definition is a bit unclear in this respect, IMHO.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>- page 9, first para has =
some strange line break, between "...network" and =
"management..."</div><div><br =
class=3D"webkit-block-placeholder"></div><div>- page 9: para starting =
with "Policy control..." refers to qos-auth which is a I-D. Do we still =
need to point to this draft and if yes, why it is happening here in the =
introduction and not in the appropriate section?</div><div><br =
class=3D"webkit-block-placeholder"></div><div>- page 11, first para =
(cont'd from previous page): s/source of the each/source of =
each</div><div><br class=3D"webkit-block-placeholder"></div><div>- page =
11, section 3.1.2, third para, refers to the QSPEC as "ongoing effort" =
which is hopefully not true anymore. Rephrasing would be =
good.</div><div><br class=3D"webkit-block-placeholder"></div><div>- page =
12, the para before the last para, "QoS models..." again refers to the =
QSPEC draft, seems to=A0superfluous=A0in this section.=A0</div><div><br =
class=3D"webkit-block-placeholder"></div><div>- page 14, third para =
refers to nslp-auth draft. As we won't have this draft as WG item, it is =
appropriate to remove the reference here and also from =A0the reference =
section</div><div><br class=3D"webkit-block-placeholder"></div><div>- =
page 16, last para, s/a =
unidirectional/an=A0unidirectional</div><div><br></div><div>- page =
20,=A0the para before the last para refers to "middle of session". What =
is "middle of session"?</div><div><br =
class=3D"webkit-block-placeholder"></div><div>- page 21, para before =
section 3.2.12.1 seems to belong in section=A03.2.12.1</div><div><br =
class=3D"webkit-block-placeholder"></div><div>- page 24, section 3.2.12 =
it would be nice to refer to 5.2.5.2 here, so that people can jump there =
to see the solution, if desired, and the more exhaustive =
explanation</div><div><br class=3D"webkit-block-placeholder"></div><div>- =
page 34, last para of section 4.5 has a self-reference to section 4.5 =
but claiming that it is different.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>- page 42, middle of page =
says three flags, but there are four of them.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>- page 45, second para =
says "Retransmissions SHOULD be disabled." If haven't understood on =
which level the retransmission should be disabled (GIST or NSLP =
level?).=A0</div><div><br class=3D"webkit-block-placeholder"></div><div>- =
page 70, section 5.3.7, first para, last sentence: at locationg i refer. =
Needs to be fixed somehow.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>- page 74, section 5.4.1, =
list end of the page: s/The SCOPING/the SCOPING. also for following =
bullets. Also for the list on =A0page 75.</div><div><br =
class=3D"webkit-block-placeholder"></div><div><div>- Section 5.4.1 and =
5.4.2 say=A0</div><div><div>..."monitored.=A0=A0 If they differ then the =
BREAK flag of new generated messages (e.g.,=A0=A0QUERY, RESERVE or =
RESPONSE) SHOULD be set.=A0 In situations ..."</div><div>Would =
RECOMMENDED be more appropriate here? (of course considering also the =
case described after ("...BREAK flag MUST not be =
set...").=A0</div><div><br class=3D"webkit-block-placeholder"></div><div>-=
 page 76, last para: "Note that QUERY messages with the RESERVE-INIT =
flag set MUST be=A0answered by the QNI." Shouldn't it read "...answered =
by the QNR."?</div><div><br =
class=3D"webkit-block-placeholder"></div><div>- page 79, section 6 (but =
not going in 6.1 and subsequent): The lists are broken (formatting =
issue)</div><div><br class=3D"webkit-block-placeholder"></div><div>- =
page 90: Appendix A. It would be good to add something along "This =
appendix is informational only."</div><div><br></div></div></div><div>- =
page 95: Heading has two times "Appendix B".</div><div><br =
class=3D"webkit-block-placeholder"></div><div><br =
class=3D"webkit-block-placeholder"></div><div>That's it.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Thanks!</div><div><br =
class=3D"webkit-block-placeholder"></div><div>=A0=A0Martin</div><div><br =
class=3D"webkit-block-placeholder"></div><div>*********</div><div>ID =
=A0Nits:</div><div><br =
class=3D"webkit-block-placeholder"></div><div><div>idnits 2.05.03=A0</div>=
 <div><br></div> <div>tmp/draft-ietf-nsis-qos-nslp-15.txt:</div> =
<div><br></div> <div>=A0 Checking boilerplate required by RFC 3978 and =
3979, updated by RFC 4748:</div> <div>=A0 =
--------------------------------------------------------------------------=
--</div> <div><br></div> <div>=A0=A0 =A0 No issues found here.</div> =
<div><br></div> <div>=A0 Checking nits according to <a =
href=3D"http://www.ietf.org/ietf/1id-guidelines.txt">http://www.ietf.org/i=
etf/1id-guidelines.txt</a>:</div> <div>=A0 =
--------------------------------------------------------------------------=
--</div> <div><br></div> <div>=A0=A0 =A0 No issues found here.</div> =
<div><br></div> <div>=A0 Checking nits according to <a =
href=3D"http://www.ietf.org/ID-Checklist.html">http://www.ietf.org/ID-Chec=
klist.html</a>:</div> <div>=A0 =
--------------------------------------------------------------------------=
--</div> <div><br></div> <div>=A0=A0 =A0 No issues found here.</div> =
<div><br></div> <div>=A0 Miscellaneous warnings:</div> <div>=A0 =
--------------------------------------------------------------------------=
--</div> <div><br></div> <div>=A0 =3D=3D The copyright year in the IETF =
Trust Copyright Line does not match the</div> <div>=A0=A0 =A0 current =
year</div> <div><br></div> <div>=A0 =3D=3D Using lowercase 'not' =
together with uppercase 'MUST' is not an accepted</div> <div>=A0=A0 =A0 =
usage according to RFC 2119.=A0 Please use 'MUST NOT' (if that is what =
you</div> <div>=A0=A0 =A0 mean).</div> <div>=A0 =A0 =A0</div> <div>=A0=A0 =
=A0 Found 'MUST not' in this paragraph:</div> <div>=A0 =A0 =A0</div> =
<div>=A0=A0 =A0 If a stateful QoS NSLP QNE receives a QUERY message with =
the</div> <div>=A0=A0 =A0 RESERVE-INIT flag and BREAK flag set then the =
BREAK flag of new generated</div> <div>=A0=A0 =A0 messages (e.g., QUERY, =
RESERVE or RESPONSE) MUST be set.=A0 When a stateful</div> <div>=A0=A0 =A0=
 QoS NSLP QNE receives a QUERY message with the the RESERVE-INIT flag =
set</div> <div>=A0=A0 =A0 and BREAK flag not set then then the IP-TTL =
and Original-TTL values in</div> <div>=A0=A0 =A0 GIST RecvMessage =
primitive MUST be monitored. If they differ then the</div> <div>=A0=A0 =A0=
 BREAK flag of new generated messages (e.g., QUERY, RESERVE or =
RESPONSE)</div> <div>=A0=A0 =A0 SHOULD be set.=A0 In situations where a =
QNE or a domain is able to provide</div> <div>=A0=A0 =A0 QoS using other =
means, see Section 3.3.5, then the BREAK flag MUST not be</div> <div>=A0=A0=
 =A0 set.</div> <div><br></div> <div><br></div> <div>=A0 Checking =
references for intended status: Proposed Standard</div> <div>=A0 =
--------------------------------------------------------------------------=
--</div> <div><br></div> <div>=A0=A0 =A0 (See RFC 3967 for information =
about using normative references to</div> <div>=A0=A0 =A0 lower-maturity =
documents in RFCs)</div> <div><br></div> <div>=A0 =3D=3D Outdated =
reference: A later version (-18) exists of</div> <div>=A0=A0 =A0 =
draft-ietf-nsis-qspec-17</div> <div><br></div> <div>=A0 =3D=3D Outdated =
reference: A later version (-08) exists of</div> <div>=A0=A0 =A0 =
draft-ietf-nsis-applicability-mobility-signaling-07</div> =
<div><br></div> <div>=A0 =3D=3D Outdated reference: A later version =
(-12) exists of</div> <div>=A0=A0 =A0 draft-ietf-nsis-rmd-10</div> =
<div><br></div> <div><br></div> <div>=A0=A0 =A0 Summary: 0 errors (**), =
5 warnings (=3D=3D), 0 comments (--).</div> =
<div>---------------------------------------------------------------------=
-----------</div><br><div> <span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div><a =
href=3D"mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</a></d=
iv><div><br></div><div><div>NEC Laboratories Europe - Network Research =
Division</div><div><br class=3D"webkit-block-placeholder"></div><div>NEC =
Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014</div></div></span> =
</div><br></div></body></html>=

--Apple-Mail-7-306019039--



--===============1168222975==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1168222975==--





From nsis-bounces@ietf.org Wed Jan 16 07:48:15 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JF7gj-0001Q0-Uk; Wed, 16 Jan 2008 07:48:13 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JF7gj-0001Pv-9i
	for nsis-confirm+ok@megatron.ietf.org; Wed, 16 Jan 2008 07:48:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JF7gi-0001Pm-WF
	for nsis@ietf.org; Wed, 16 Jan 2008 07:48:13 -0500
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JF7gg-0004es-I5
	for nsis@ietf.org; Wed, 16 Jan 2008 07:48:12 -0500
Received: from sbz-31.cs.helsinki.fi (sbz-31.cs.helsinki.fi [128.214.9.99])
	(TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.cs.helsinki.fi with esmtp; Wed, 16 Jan 2008 14:48:05 +0200
	id 000805C9.478DFD05.00004F96
Date: Wed, 16 Jan 2008 14:48:05 +0200 (EET)
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Martin Stiemerling <stiemerling@netlab.nec.de>
Subject: Re: [NSIS] Review of draft-ietf-nsis-qos-nslp-15.txt
In-Reply-To: <C7D86860-A84B-4F94-84C2-FD73665A44D9@netlab.nec.de>
Message-ID: <Pine.LNX.4.64.0801161447360.7116@sbz-31.cs.Helsinki.FI>
References: <C7D86860-A84B-4F94-84C2-FD73665A44D9@netlab.nec.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d
Cc: nsis <nsis@ietf.org>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org


Thanks Martin!

I'll update the draft, and resubmit it as soon as possible.

Jukka

On Tue, 8 Jan 2008, Martin Stiemerling wrote:

> Hi all,
> 
> Here is my chair's review of draft-ietf-nsis-qos-nslp-15.txt.
> 
> I have reviewed the whole draft and do not see any issue with it. It is
> written in an excellent way and seems to be just fine. Thanks to all who
> contributed and especially to the editors.
> 
> The comments are just editorial or minor clarifications. Please fix them if
> possible and submit a new version.
> 
> Editorial issues:
> 
> - ID nits throws some output (see attached at bottom of this mail). The only
> relevant is an editorial nit; 2nd under "miscellaneous warnings".
> 
> - page 6, definition of session: " A session defines an association between a
> QNI and QNR related to a data flow." Just for my understanding: This sounds
> such as the involved QNEs on the path are not part of the session? The
> definition is a bit unclear in this respect, IMHO.
> 
> - page 9, first para has some strange line break, between "...network" and
> "management..."
> 
> - page 9: para starting with "Policy control..." refers to qos-auth which is a
> I-D. Do we still need to point to this draft and if yes, why it is happening
> here in the introduction and not in the appropriate section?
> 
> - page 11, first para (cont'd from previous page): s/source of the each/source
> of each
> 
> - page 11, section 3.1.2, third para, refers to the QSPEC as "ongoing effort"
> which is hopefully not true anymore. Rephrasing would be good.
> 
> - page 12, the para before the last para, "QoS models..." again refers to the
> QSPEC draft, seems to superfluous in this section.
> 
> - page 14, third para refers to nslp-auth draft. As we won't have this draft
> as WG item, it is appropriate to remove the reference here and also from  the
> reference section
> 
> - page 16, last para, s/a unidirectional/an unidirectional
> 
> - page 20, the para before the last para refers to "middle of session". What
> is "middle of session"?
> 
> - page 21, para before section 3.2.12.1 seems to belong in section 3.2.12.1
> 
> - page 24, section 3.2.12 it would be nice to refer to 5.2.5.2 here, so that
> people can jump there to see the solution, if desired, and the more exhaustive
> explanation
> 
> - page 34, last para of section 4.5 has a self-reference to section 4.5 but
> claiming that it is different.
> 
> - page 42, middle of page says three flags, but there are four of them.
> 
> - page 45, second para says "Retransmissions SHOULD be disabled." If haven't
> understood on which level the retransmission should be disabled (GIST or NSLP
> level?).
> 
> - page 70, section 5.3.7, first para, last sentence: at locationg i refer.
> Needs to be fixed somehow.
> 
> - page 74, section 5.4.1, list end of the page: s/The SCOPING/the SCOPING.
> also for following bullets. Also for the list on  page 75.
> 
> - Section 5.4.1 and 5.4.2 say
> ..."monitored.   If they differ then the BREAK flag of new generated messages
> (e.g.,  QUERY, RESERVE or RESPONSE) SHOULD be set.  In situations ..."
> Would RECOMMENDED be more appropriate here? (of course considering also the
> case described after ("...BREAK flag MUST not be set...").
> 
> - page 76, last para: "Note that QUERY messages with the RESERVE-INIT flag set
> MUST be answered by the QNI." Shouldn't it read "...answered by the QNR."?
> 
> - page 79, section 6 (but not going in 6.1 and subsequent): The lists are
> broken (formatting issue)
> 
> - page 90: Appendix A. It would be good to add something along "This appendix
> is informational only."
> 
> - page 95: Heading has two times "Appendix B".
> 
> 
> That's it.
> 
> Thanks!
> 
>  Martin
> 
> *********
> ID  Nits:
> 
> idnits 2.05.03
> 
> tmp/draft-ietf-nsis-qos-nslp-15.txt:
> 
>  Checking boilerplate required by RFC 3978 and 3979, updated by RFC 4748:
>  ----------------------------------------------------------------------------
> 
>     No issues found here.
> 
>  Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt:
>  ----------------------------------------------------------------------------
> 
>     No issues found here.
> 
>  Checking nits according to http://www.ietf.org/ID-Checklist.html:
>  ----------------------------------------------------------------------------
> 
>     No issues found here.
> 
>  Miscellaneous warnings:
>  ----------------------------------------------------------------------------
> 
>  == The copyright year in the IETF Trust Copyright Line does not match the
>     current year
> 
>  == Using lowercase 'not' together with uppercase 'MUST' is not an accepted
>     usage according to RFC 2119.  Please use 'MUST NOT' (if that is what you
>     mean).
> 
>     Found 'MUST not' in this paragraph:
> 
>     If a stateful QoS NSLP QNE receives a QUERY message with the
>     RESERVE-INIT flag and BREAK flag set then the BREAK flag of new generated
>     messages (e.g., QUERY, RESERVE or RESPONSE) MUST be set.  When a stateful
>     QoS NSLP QNE receives a QUERY message with the the RESERVE-INIT flag set
>     and BREAK flag not set then then the IP-TTL and Original-TTL values in
>     GIST RecvMessage primitive MUST be monitored. If they differ then the
>     BREAK flag of new generated messages (e.g., QUERY, RESERVE or RESPONSE)
>     SHOULD be set.  In situations where a QNE or a domain is able to provide
>     QoS using other means, see Section 3.3.5, then the BREAK flag MUST not be
>     set.
> 
> 
>  Checking references for intended status: Proposed Standard
>  ----------------------------------------------------------------------------
> 
>     (See RFC 3967 for information about using normative references to
>     lower-maturity documents in RFCs)
> 
>  == Outdated reference: A later version (-18) exists of
>     draft-ietf-nsis-qspec-17
> 
>  == Outdated reference: A later version (-08) exists of
>     draft-ietf-nsis-applicability-mobility-signaling-07
> 
>  == Outdated reference: A later version (-12) exists of
>     draft-ietf-nsis-rmd-10
> 
> 
>     Summary: 0 errors (**), 5 warnings (==), 0 comments (--).
> --------------------------------------------------------------------------------
> 
> stiemerling@netlab.nec.de
> 
> 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
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Mon Jan 21 02:58:54 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JGrYT-0008Js-A2; Mon, 21 Jan 2008 02:58:53 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JGrYS-0008Jm-Nr
	for nsis-confirm+ok@megatron.ietf.org; Mon, 21 Jan 2008 02:58:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JGrYL-0008Dl-Jd
	for nsis@ietf.org; Mon, 21 Jan 2008 02:58:45 -0500
Received: from mail.gmx.net ([213.165.64.20])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1JGrYK-0006Q8-S1
	for nsis@ietf.org; Mon, 21 Jan 2008 02:58:45 -0500
Received: (qmail invoked by alias); 21 Jan 2008 07:52:03 -0000
Received: from proxy1-nsn.nsn-inter.net (EHLO [217.115.75.229])
	[217.115.75.229]
	by mail.gmx.net (mp032) with SMTP; 21 Jan 2008 08:52:03 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18UxUUlns8UUT3PGiCGM8xdI/5yGTrlxa68NEIaRp
	tEL3PN56wLCHQH
Message-ID: <47944F22.1080901@gmx.net>
Date: Mon, 21 Jan 2008 09:52:02 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: keyprov@ietf.org, dime@ietf.org, ECRIT <ecrit@ietf.org>, 
	"nsis@ietf.org" <nsis@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: 
Subject: [NSIS] FW: Internet-Drafts Submission Cutoff Dates for the 71st
 IETF Meeting in Philadelphia, PA, USA
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org

Please keep the deadlines in mind.

Ciao
Hannes

-----Original Message-----
From: ietf-secretariat@ietf.org [mailto:ietf-secretariat@ietf.org] 
Sent: Friday, January 18, 2008 12:00 AM
To: ietf-announce@ietf.org
Subject: Internet-Drafts Submission Cutoff Dates for the 71st IETF Meeting in Philadelphia, PA, USA


There are two (2) Internet-Draft cutoff dates for the 71st 
IETF Meeting in Philadelphia, PA, USA:

February 18th: Cutoff Date for Initial (i.e., version -00) 
Internet-Draft Submissions 

All initial Internet-Drafts (version -00) must be submitted by Monday, 
February 18th at 9:00 AM ET (14:00 UTC/GMT).The only exception is for
version -00 WG drafts that replace existing non-WG drafts.  Such drafts
may be submitted until the cutoff date for version -01 and higher
drafts.
As always, all initial submissions with a filename beginning with 
"draft-ietf" must be approved by the appropriate WG Chair before they 
can be processed or announced.  The Secretariat would appreciate 
receiving WG Chair approval by Monday, February 11th at 9:00 AM ET (14:00 UTC/GMT).

February  (14:00 UTC/GMT): Cutoff Date for Revised (i.e., version -01 and higher) 
Internet-Draft Submissions 

All revised Internet-Drafts (version -01 and higher) must be submitted 
by Monday, February 25th at 9:00 AM ET (14:00 UTC/GMT).

Initial and revised Internet-Drafts received after their respective 
cutoff dates will not be made available in the Internet-Drafts 
directory or announced until on or after Monday, March 10th at 9:00 
AM ET (13:00 UTC/GMT), when Internet-Draft posting resumes.  Please do not wait until 
the last minute to submit.

The Secretariat encourages you to submit your Internet-Drafts via the 
Internet-Draft Submission Tool (IDST) https://datatracker.ietf.org/idst/upload.cgi. 
If you are unable to do so, then you may still submit your Internet-
Drafts manually by sending them to internet-drafts@ietf.org.  If you 
are submitting a version -00 WG draft that replaces non-WG draft, then 
you must submit it manually as the current IDST cannot handle 
replacements.  Please be sure to state that one draft replaces another 
in the cover note that accompanies your submission.  Also, please note 
that the IDST will not accept drafts submitted after their respective 
cutoff dates.

Thank you for your understanding and cooperation. If you have any 
questions or concerns, then please send a message to 
internet-drafts@ietf.org.

The IETF Secretariat

FYI: The Internet-Draft cutoff dates as well as other significant dates
for the 71st IETF Meeting can be found at http://www.ietf.org/meetings/71-cutoff_dates.html.



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



From nsis-bounces@ietf.org Mon Jan 21 07:39:33 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JGvvx-0000Rb-QG; Mon, 21 Jan 2008 07:39:25 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JGvvw-0000RW-6J
	for nsis-confirm+ok@megatron.ietf.org; Mon, 21 Jan 2008 07:39:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JGvvv-0000RO-SX
	for nsis@ietf.org; Mon, 21 Jan 2008 07:39:23 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JGvvu-0003lO-JO
	for nsis@ietf.org; Mon, 21 Jan 2008 07:39:23 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 2F8D228000357
	for <nsis@ietf.org>; Mon, 21 Jan 2008 13:39:22 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8UHV8iajTGyU for <nsis@ietf.org>;
	Mon, 21 Jan 2008 13:39:22 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 0B4DE28000356
	for <nsis@ietf.org>; Mon, 21 Jan 2008 13:39:17 +0100 (CET)
Received: from [10.1.1.109] ([10.1.1.109]) by mx1.office over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 21 Jan 2008 13:39:16 +0100
Mime-Version: 1.0 (Apple Message framework v753)
To: nsis <nsis@ietf.org>
Message-Id: <B31D515A-3195-45E0-A587-E727472F035A@netlab.nec.de>
References: <E1JFmSH-0000c6-Rd@stiedprstage1.ietf.org>
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Date: Mon, 21 Jan 2008 13:39:16 +0100
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 21 Jan 2008 12:39:16.0804 (UTC)
	FILETIME=[A2B26040:01C85C2A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 16a2b98d831858659c646b3dec9ed22b
Subject: [NSIS] Fwd: I-D Action:draft-manner-nsis-user-guide-00.txt 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1919825970=="
Errors-To: nsis-bounces@ietf.org


--===============1919825970==
Content-Type: multipart/alternative; boundary=Apple-Mail-14--726342402


--Apple-Mail-14--726342402
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

FYI.

Anfang der weitergeleiteten E-Mail:

> Von: Internet-Drafts@ietf.org
> Datum: 18. Januar 2008 09:20:01 MEZ
> An: i-d-announce@ietf.org
> Betreff: I-D Action:draft-manner-nsis-user-guide-00.txt
> Antwort an: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts  
> directories.
>
> 	Title           : What is Next Steps in Signaling anyway - A  
> User's Guide to the NSIS Protocol Family
> 	Author(s)       : J. Manner, R. Bless
> 	Filename        : draft-manner-nsis-user-guide-00.txt
> 	Pages           : 16
> 	Date            : 2008-01-18
>
> The Next Steps in Signaling (NSIS) Working group was officially
> formed in November 2001 to standardize a new IP signaling protocol
> suite.  Six years have now passed and the first actual protocol
> specifications have been finalized.  The purpose of this draft is to
> give an overview of what has been achieved, how the industry can make
> use of the new protocols, and how the research community can further
> extend the designs.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-manner-nsis-user- 
> guide-00.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
> 	"get draft-manner-nsis-user-guide-00.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-manner-nsis-user-guide-00.txt".
>
> NOTE:   The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID: <2008-01-18031021.I-D\@ietf.org>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce

stiemerling@netlab.nec.de

NEC Laboratories Europe - Network Research Division

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


--Apple-Mail-14--726342402
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">FYI.<br><div><br><div>Anfang =
der weitergeleiteten E-Mail:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" color=3D"#000000" =
style=3D"font: 12.0px Helvetica; color: #000000"><b>Von: =
</b></font><font face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica"><a =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a></fon=
t></div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" =
color=3D"#000000" style=3D"font: 12.0px Helvetica; color: =
#000000"><b>Datum: </b></font><font face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica">18. Januar 2008 09:20:01 =
MEZ</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font face=3D"Helvetica" =
size=3D"3" color=3D"#000000" style=3D"font: 12.0px Helvetica; color: =
#000000"><b>An: </b></font><font face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica"><a =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a></font></di=
v><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" color=3D"#000000" =
style=3D"font: 12.0px Helvetica; color: #000000"><b>Betreff: =
</b></font><font face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica"><b>I-D Action:draft-manner-nsis-user-guide-00.txt<span =
class=3D"Apple-converted-space">=A0</span></b></font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" color=3D"#000000" =
style=3D"font: 12.0px Helvetica; color: #000000"><b>Antwort an: =
</b></font><font face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica"><a =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></fon=
t></div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; min-height: 14px; "><br></div> <div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">A New Internet-Draft is available from the on-line =
Internet-Drafts directories.</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Title <span =
class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 =A0 </span>: What is =
Next Steps in Signaling anyway - A User's Guide to the NSIS Protocol =
Family</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Author(s) <span =
class=3D"Apple-converted-space">=A0 =A0 =A0 </span>: J. Manner, R. =
Bless</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Filename<span =
class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 </span>: =
draft-manner-nsis-user-guide-00.txt</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Pages =
<span class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 =A0 </span>: =
16</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Date<span =
class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 =A0 =A0 </span>: =
2008-01-18</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">The Next Steps in Signaling (NSIS) Working group was =
officially</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">formed in November 2001 to =
standardize a new IP signaling protocol</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">suite.<span class=3D"Apple-converted-space">=A0 </span>Six years have =
now passed and the first actual protocol</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">specifications have been finalized.<span =
class=3D"Apple-converted-space">=A0 </span>The purpose of this draft is =
to</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; ">give an overview of what has been achieved, how =
the industry can make</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">use of the new protocols, =
and how the research community can further</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">extend =
the designs.</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">A URL for this Internet-Draft is:</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><a =
href=3D"http://www.ietf.org/internet-drafts/draft-manner-nsis-user-guide-0=
0.txt">http://www.ietf.org/internet-drafts/draft-manner-nsis-user-guide-00=
.txt</a></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">To remove yourself from the I-D Announcement list, =
send a message to</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><a =
href=3D"mailto:i-d-announce-request@ietf.org">i-d-announce-request@ietf.or=
g</a> with the word unsubscribe in the body of<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">the =
message.</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">You can also visit <a =
href=3D"https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.=
ietf.org/mailman/listinfo/I-D-announce</a></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">to =
change your subscription settings.</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Internet-Drafts are also =
available by anonymous FTP. Login with the<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">username =
"anonymous" and a password of your e-mail address. After<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">logging =
in, type "cd internet-drafts" and then</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>"get =
draft-manner-nsis-user-guide-00.txt".</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A list of =
Internet-Drafts directories can be found in</div><div style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a =
href=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</=
a></div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; ">or <a =
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf=
/1shadow-sites.txt</a></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Internet-Drafts can also be =
obtained by e-mail.</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Send a message to:</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><a =
href=3D"mailto:mailserv@ietf.org">mailserv@ietf.org</a>.</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">In the body type:</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>"FILE =
/internet-drafts/draft-manner-nsis-user-guide-00.txt".</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">NOTE: =
<span class=3D"Apple-converted-space">=A0 </span>The mail server at =
ietf.org can return the document in</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>MIME-encoded form by using the "mpack" utility.<span =
class=3D"Apple-converted-space">=A0 </span>To use this</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>feature, insert the command =
"ENCODING mime" before the "FILE"</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>command.<span class=3D"Apple-converted-space">=A0 </span>To =
decode the response(s), you will need "munpack" or</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>a MIME-compliant mail =
reader.<span class=3D"Apple-converted-space">=A0 </span>Different =
MIME-compliant mail readers</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>exhibit =
different behavior, especially when dealing with</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>"multipart" MIME messages (i.e. =
documents which have been split</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>up into =
multiple messages), so check your local documentation on</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>how to manipulate these =
messages.</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Below is the data which will enable a MIME compliant =
mail reader</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">implementation to automatically =
retrieve the ASCII version of the</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Internet-Draft.</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-Type: =
text/plain</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Content-ID: =
&lt;2008-01-18031021.I-D\@ietf.org&gt;</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">_______________________________________________</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">I-D-Announce mailing list</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><a =
href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><a =
href=3D"https://www1.ietf.org/mailman/listinfo/i-d-announce">https://www1.=
ietf.org/mailman/listinfo/i-d-announce</a></div> =
</blockquote></div><br><div> <span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div><a =
href=3D"mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</a></d=
iv><div><br></div><div><div>NEC Laboratories Europe - Network Research =
Division</div><div><br class=3D"webkit-block-placeholder"></div><div>NEC =
Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014</div></div></span> =
</div><br></body></html>=

--Apple-Mail-14--726342402--



--===============1919825970==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1919825970==--





From nsis-bounces@ietf.org Thu Jan 24 05:22:51 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHzEF-0006r1-1I; Thu, 24 Jan 2008 05:22:39 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JHzEC-0006mM-Pd
	for nsis-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 05:22:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHzEC-0006kn-CP
	for nsis@ietf.org; Thu, 24 Jan 2008 05:22:36 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHzEA-0000VX-Dj
	for nsis@ietf.org; Thu, 24 Jan 2008 05:22:36 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 7DD4B28000625
	for <nsis@ietf.org>; Thu, 24 Jan 2008 11:22:33 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ONXbUwbyIiYd for <nsis@ietf.org>;
	Thu, 24 Jan 2008 11:22:33 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 5F87128000455
	for <nsis@ietf.org>; Thu, 24 Jan 2008 11:22:28 +0100 (CET)
Received: from [10.1.1.109] ([10.1.1.109]) by mx1.office over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 24 Jan 2008 11:22:28 +0100
Mime-Version: 1.0 (Apple Message framework v753)
To: nsis <nsis@ietf.org>
Message-Id: <5B37E709-9B27-4490-B2EF-FAB14235153E@netlab.nec.de>
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Date: Thu, 24 Jan 2008 11:22:27 +0100
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 24 Jan 2008 10:22:28.0322 (UTC)
	FILETIME=[054CAC20:01C85E73]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Subject: [NSIS] NATFW issue: state 'transit' timer definition
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2006662176=="
Errors-To: nsis-bounces@ietf.org


--===============2006662176==
Content-Type: multipart/alternative; boundary=Apple-Mail-4--475351523


--Apple-Mail-4--475351523
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

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

Hi all,

I finally found time to get back to the NATFW NSLP and your WGLC  
comments. Thanks to all who did a review and sent in their comments!

I also have done a complete review of draft-ietf-nsis-nslp- 
natfw-16.txt and found some issues to be discussed. There will be  
separate e-mails for each issue I've found.

Here we go:

In Section 3.2.8.  NATFW NSLP Signaling Sessions the different  
conceptual states of the a NATFW NSLP signaling session are defined.  
I see all states are fine except the last one which is 'transit':

Transit: The node has received an asynchronous message, i.e., a
NOTIFY, and can delete the NATFW NSLP signaling session if needed.
When a node has received a NOTIFY message (for instance,
indicating a route change) it marks it as 'Transit' and deletes
this NATFW NSLP signaling session if it is unused for some time
specific to the local node.  This idle time does not need to be
fixed, since it can depend on the node local maintenance cycle,
i.e., the NATFW NSLP signaling session could be deleted if the
node runs it garbage collection cycle.

The issue is see, is the undefined timer value in this state. It  
simply says "...for some time..." which can result in implementations  
removing state immediately (time = 0), wait for seconds or minutes,  
or do never remove the state (would be a bug indeed).

I personally would prefer to either give a fixed value or to give a  
formula to calculate this time in a standardised way.

My proposal: Set this timer to 30 seconds fixed, as if there is no  
updating CREATE or EXTERNAL message within 30 seconds to a 'transit'  
state there won't be anything beyond this anymore.

   Martin

stiemerling@netlab.nec.de

NEC Laboratories Europe - Network Research Division

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


--Apple-Mail-4--475351523
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
[writing with chair's hat off, i.e., as NATFW NSLP author only!]<div><br =
class=3D"webkit-block-placeholder"></div><div>Hi all,</div><div><br =
class=3D"webkit-block-placeholder"></div><div>I finally found time to =
get back to the NATFW NSLP and your WGLC comments. Thanks to all who did =
a review and sent in their comments!</div><div><br></div><div>I also =
have done a complete review of=A0draft-ietf-nsis-nslp-natfw-16.txt and =
found some issues to be discussed. There will be separate e-mails for =
each issue I've found.=A0</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Here we go:</div><div><br =
class=3D"webkit-block-placeholder"></div><div>In Section=A03.2.8.=A0 =
NATFW NSLP Signaling Sessions the different conceptual states of the a =
NATFW NSLP signaling session are defined. I see all states are fine =
except the last one which is 'transit':</div><div><br =
class=3D"webkit-block-placeholder"></div><div><div>Transit: The node has =
received an asynchronous message, i.e., a</div><div>NOTIFY, and can =
delete the NATFW NSLP signaling session if needed.</div><div>When a node =
has received a NOTIFY message (for instance,</div><div>indicating a =
route change) it marks it as 'Transit' and deletes</div><div>this NATFW =
NSLP signaling session if it is unused for some time</div><div>specific =
to the local node. =A0This idle time does not need to =
be</div><div>fixed, since it can depend on the node local maintenance =
cycle,</div><div>i.e., the NATFW NSLP signaling session could be deleted =
if the</div><div>node runs it garbage collection =
cycle.</div></div><div><br =
class=3D"webkit-block-placeholder"></div><div>The issue is see, is the =
undefined timer value in this state. It simply says "...for some =
time..." which can result in implementations removing state immediately =
(time =3D 0), wait for seconds or minutes, or do never remove the state =
(would be a bug indeed).=A0</div><div><br =
class=3D"webkit-block-placeholder"></div><div>I personally would prefer =
to either give a fixed value or to give a formula to calculate this time =
in a=A0standardised=A0way.=A0</div><div><br =
class=3D"webkit-block-placeholder"></div><div>My proposal: Set this =
timer to 30 seconds fixed, as if there is no updating CREATE or EXTERNAL =
message within 30 seconds to a 'transit' state there won't be anything =
beyond this anymore.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>=A0=A0Martin<br><br><div> =
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
auto; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div><a =
href=3D"mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</a></d=
iv><div><br></div><div><div>NEC Laboratories Europe - Network Research =
Division</div><div><br class=3D"webkit-block-placeholder"></div><div>NEC =
Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014</div></div></span> =
</div><br></div></body></html>=

--Apple-Mail-4--475351523--



--===============2006662176==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============2006662176==--





From nsis-bounces@ietf.org Thu Jan 24 05:39:46 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHzUo-0004dr-3F; Thu, 24 Jan 2008 05:39:46 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JHzUm-0004ZC-6v
	for nsis-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 05:39:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHzUl-0004Z4-TO
	for nsis@ietf.org; Thu, 24 Jan 2008 05:39:43 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHzUl-0000qm-82
	for nsis@ietf.org; Thu, 24 Jan 2008 05:39:43 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id CB68E28000356
	for <nsis@ietf.org>; Thu, 24 Jan 2008 11:39:42 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XdMBdAEZTbWo for <nsis@ietf.org>;
	Thu, 24 Jan 2008 11:39:42 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id ADA792800034F
	for <nsis@ietf.org>; Thu, 24 Jan 2008 11:39:37 +0100 (CET)
Received: from [10.1.1.109] ([10.1.1.109]) by mx1.office over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 24 Jan 2008 11:39:37 +0100
Mime-Version: 1.0 (Apple Message framework v753)
To: nsis <nsis@ietf.org>
Message-Id: <23EEB316-B5AC-48B7-BC9B-373FB0BC51EA@netlab.nec.de>
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Date: Thu, 24 Jan 2008 11:39:37 +0100
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 24 Jan 2008 10:39:37.0646 (UTC)
	FILETIME=[6AD30CE0:01C85E75]
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Subject: [NSIS] NATFW issue: Lifetime error messages
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0580084666=="
Errors-To: nsis-bounces@ietf.org


--===============0580084666==
Content-Type: multipart/alternative; boundary=Apple-Mail-6--474322078


--Apple-Mail-6--474322078
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

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

Hi all,

When reading Section 3.4.  Calculation of Signaling Session Lifetime  
I stumbled over the error messages send when NFs or the NR reject the  
session lifetime.

Currently, there are two error codes (thus also cases) defined:
0x02: Requested lifetime is too big.
0x10: Requested lifetime is too small.

These two error cases are used to tell the NI whether the requested  
lifetime has an issue *and* if the by an NF/NR modified lifetime has  
an issue (see Section 3.4 before figure 12). This is a bit  
overloaded, as the NI eventually cannot tell whether his lifetime  
proposal was bad or if the en-route changed lifetime as bad.

My change proposal:
Keep these error codes 0x02 and 0x10 for rejection of NI's lifetime  
proposal and add two new error codes for rejection of a modified  
lifetime:
0xXY: Modified lifetime is too big.
0xSD: Modified lifetime is too small.
(0xXY and 0xSD must be replaced by real number later on)

Those messages are generated as an error response if one of the NFs  
or the NR has changed in away that other NFs cannot accept it  
anymore. This, at least, gives the NI the hint that the NFs/NR on the  
way have some trouble on agreeing a lifetime value.


   Martin

stiemerling@netlab.nec.de

NEC Laboratories Europe - Network Research Division

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


--Apple-Mail-6--474322078
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
[writing with chair's hat off, i.e., as NATFW NSLP author only!]<div><br =
class=3D"webkit-block-placeholder"></div><div>Hi all,</div><div><br =
class=3D"webkit-block-placeholder"></div><div>When reading Section=A03.4.=A0=
 Calculation of Signaling Session Lifetime I stumbled over the error =
messages send when NFs or the NR reject the session =
lifetime.=A0</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Currently, there are two =
error codes (thus also cases) defined:</div><div><div><div>0x02: =
Requested lifetime is too big.</div></div><div>0x10: Requested lifetime =
is too small.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>These two error cases are =
used to tell the NI whether the requested lifetime has an issue *and* if =
the by an NF/NR modified lifetime has an issue (see Section 3.4 before =
figure 12). This is a bit overloaded, as the NI eventually cannot tell =
whether his lifetime proposal was bad or if the en-route changed =
lifetime as bad.=A0</div><div><br =
class=3D"webkit-block-placeholder"></div><div>My change =
proposal:</div><div>Keep these error codes 0x02 and 0x10 for rejection =
of NI's lifetime proposal and add two new error codes for rejection of a =
modified lifetime:</div><div>0xXY: Modified lifetime is too =
big.</div><div>0xSD: Modified lifetime is too small.</div><div>(0xXY and =
0xSD must be replaced by real number later on)</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Those messages are =
generated as an error response if one of the NFs or the NR has changed =
in away that other NFs cannot accept it anymore. This, at least, gives =
the NI the hint that the NFs/NR on the way have some trouble on agreeing =
a lifetime value.</div><div><br =
class=3D"webkit-block-placeholder"></div><div><br></div></div><div>=A0=A0M=
artin<br><br><div> <span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Lucida Grande'; font-size: 12px; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div><a =
href=3D"mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</a></d=
iv><div><br></div><div><div>NEC Laboratories Europe - Network Research =
Division</div><div><br class=3D"webkit-block-placeholder"></div><div>NEC =
Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014</div></div></span> =
</div><br></div></body></html>=

--Apple-Mail-6--474322078--



--===============0580084666==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0580084666==--





From nsis-bounces@ietf.org Thu Jan 24 05:45:42 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHzaX-0001r8-Nj; Thu, 24 Jan 2008 05:45:41 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JHzaW-0001q0-LA
	for nsis-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 05:45:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHzaW-0001ps-BY
	for nsis@ietf.org; Thu, 24 Jan 2008 05:45:40 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHzaT-0000wq-Um
	for nsis@ietf.org; Thu, 24 Jan 2008 05:45:40 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 845A928000356
	for <nsis@ietf.org>; Thu, 24 Jan 2008 11:45:37 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zL++e8eCaO-s for <nsis@ietf.org>;
	Thu, 24 Jan 2008 11:45:37 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 66D972800034F
	for <nsis@ietf.org>; Thu, 24 Jan 2008 11:45:32 +0100 (CET)
Received: from [10.1.1.109] ([10.1.1.109]) by mx1.office over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 24 Jan 2008 11:45:32 +0100
Mime-Version: 1.0 (Apple Message framework v753)
To: nsis <nsis@ietf.org>
Message-Id: <1877E81B-5AE0-435C-AD64-92A273947A76@netlab.nec.de>
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Date: Thu, 24 Jan 2008 11:45:31 +0100
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 24 Jan 2008 10:45:32.0355 (UTC)
	FILETIME=[3E3F5930:01C85E76]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Subject: [NSIS] NATFW issue: proxy flag handling
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0068718275=="
Errors-To: nsis-bounces@ietf.org


--===============0068718275==
Content-Type: multipart/alternative; boundary=Apple-Mail-7--473967497


--Apple-Mail-7--473967497
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

[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


stiemerling@netlab.nec.de

NEC Laboratories Europe - Network Research Division

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


--Apple-Mail-7--473967497
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<div>[writing with chair's hat off, i.e., as NATFW NSLP author =
only!]<br><br><div>Hi all,</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Section=A04.1. =A0"NSLP =
Header" also defines some processing for the proxy (p) flag and the =
different messages.=A0</div><div>The text:</div><div><div>The P flag =
indicates the usage of proxy mode. =A0If proxy mode is used</div><div>it =
MUST be set to 1. =A0Proxy mode usage is only allowed in =
combination</div><div>with the message types CREATE and EXTERNAL, P=3D1 =
MUST NOT be set with</div><div>message types other than CREATE and =
EXTERNAL. =A0The P flag MUST be</div><div>ignored when processing =
messages with type RESPONSE. =A0An error</div><div>RESPONSE message of =
class 'Protocol error' (0x3) and type 'Bad flags</div><div>value' (0x03) =
MUST be generated, if the P flag is set in =
NOTIFY</div><div>messages.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>It's strange that the P =
flag must be ignored for RESPONSE but generates an error for =
NOTIFY.=A0</div><div><br class=3D"webkit-block-placeholder"></div><div><br=
 class=3D"webkit-block-placeholder"></div><div>Change =
proposal:</div><div>OLD:</div><div><div>The P flag MUST be=A0ignored =
when processing messages with type RESPONSE. =A0An error RESPONSE =
message of class 'Protocol error' (0x3) and type 'Bad flags=A0value' =
(0x03) MUST be generated, if the P flag is set in NOTIFY=A0</div><div><br =
class=3D"webkit-block-placeholder"></div><div>NEW:</div></div><div>The P =
flag MUST be=A0ignored when processing messages with type RESPONSE and =
NOTIFY.=A0</div><div><br class=3D"webkit-block-placeholder"></div><div><br=
 class=3D"webkit-block-placeholder"></div><div><br =
class=3D"webkit-block-placeholder"></div><div>The P flag is anyhow =
meaningless with those two message =
types.=A0</div></div><div>=A0=A0</div><div>=A0Martin</div></div><br><br><d=
iv> <span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
auto; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div><a =
href=3D"mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</a></d=
iv><div><br></div><div><div>NEC Laboratories Europe - Network Research =
Division</div><div><br class=3D"webkit-block-placeholder"></div><div>NEC =
Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014</div></div></span> =
</div><br></body></html>=

--Apple-Mail-7--473967497--



--===============0068718275==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0068718275==--





From nsis-bounces@ietf.org Thu Jan 24 09:03:13 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JI2fg-00021D-HV; Thu, 24 Jan 2008 09:03:12 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JI2ff-00020s-3U
	for nsis-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 09:03:11 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JI2fe-00020k-Lp
	for nsis@ietf.org; Thu, 24 Jan 2008 09:03:10 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JI2fc-0005Ab-AV
	for nsis@ietf.org; Thu, 24 Jan 2008 09:03:10 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id A912928000459;
	Thu, 24 Jan 2008 15:03:07 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4Dnp+XTFe6aX; Thu, 24 Jan 2008 15:03:07 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 829A528000455;
	Thu, 24 Jan 2008 15:02:57 +0100 (CET)
Received: from [10.1.1.109] ([10.1.1.109]) by mx1.office over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 24 Jan 2008 15:02:57 +0100
In-Reply-To: <Pine.LNX.4.64.0712042046330.9630@sbz-31.cs.Helsinki.FI>
References: <57BCC14C-53FD-4B9C-8EEE-C2D5D78B0B1F@netlab.nec.de>
	<Pine.LNX.4.64.0712042046330.9630@sbz-31.cs.Helsinki.FI>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <B198792F-E794-40A1-9316-5DEDAF7A2DD6@netlab.nec.de>
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Subject: Re: [NSIS] WGLC: draft-ietf-nsis-nslp-natfw-16.txt
Date: Thu, 24 Jan 2008 15:02:56 +0100
To: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 24 Jan 2008 14:02:57.0442 (UTC)
	FILETIME=[D2783020:01C85E91]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c6d4566aad1fef50f784fa8a77ccada7
Cc: nsis <nsis@ietf.org>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0083494804=="
Errors-To: nsis-bounces@ietf.org


--===============0083494804==
Content-Type: multipart/alternative; boundary=Apple-Mail-12--462122613


--Apple-Mail-12--462122613
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hi Jukka,

Thanks for the review and more inline.

   Martin

Am 04.12.2007 um 23:06 schrieb Jukka MJ Manner:

>
> Hi,
>
> I have reviewed that draft. I don't have any major objections to the
> document, just some miscellaneous comments and clarification requests.
>
> Here goes:
>
> - p.6, bullet 1: at this point in the document, it is not clear to the
>   reader what the NSIS initiator/receiver are. Propose to use simpler
>   terminology at this early phase in the intro.

Fixed. E.g., s/NSIS initiator/initiator of the NSIS signaling

>
> - p.6, end of page: propose to clearly say wo sends which message,  
> e.g.:
>
> "CREATE message: send by the data sender for..."
>
> "EXTERNAL message: used by data receiver to ..."

Fixed.

>
> Related comment: why abbreviate EXTERNAL to "EXT"?
> 	* None of the other message are abbreviated
> 	* EXTERNAL is as long a word as "RESPONSE" (both abbreviated?)
>
> Suggest to drop the EXT-term

Done and I have changed to EXTERNAL in all occurrences,

>
> Related to the above the document presents over and over again that
> EXTERNAL is EXT ("EXTERNAL (EXT)") and is a bit inconsistent in  
> when to
> use EXTERNAL and when just EXT (both used here and there).

Fixed, as it is called EXTERNAL only now.

>
> - p.7.: s/body of the document, covers/body of the document cover/

Fixed.

>
> - p.23: s/inSection/in Section/

Fixed.

>
> - p.27: "if the node runs _it_ garbage collection cycle."?

Fixed.

>
> - p.27: "appropriate error of class 'Protocol error' (0x1)": 0x1 is
>   Informational, ox3 is protocol error.

Fixed.

>
> - p.32: "is thus managed NSLP hop-by-hop"?

Fixed.

>
> - p.41: "session created by REA."?

Fixed.

>
> - p.41: "using CREATE Section 3.7.1" > "(see Section 3.7.1)"?

Fixed.

>
> - p.43: "if the like to aggregate"?

Fixed.

>
> - p.46, whole Section 3.7.6.1: should NR be actually DR? Including  
> Figure
>   18?

I prefer to leave NR in the text, but have added the term DR to  
figure 18. This should make it clear.

>
> - P.46-47, Section 3.7.6.1: I don't really get this operation at all.
>   Sounds a bit complex to have the EXT-session trigger a CREATE- 
> session.

That's the best way ensure faith sharing between both of them. The  
CREATE session should die together with the EXTERNAL-PROXY session.

>   Maybe some more discussion/description is needed to open up the
>   scenario. Also, the NATFW_NONCE sounds a bit wierd, somehow. In  
> the QoS

Added some text to actually describe the dependency between the  
sessions of EXTERNAL and CREATE.

>   NSLP, we have the same functionality, but it is called "session  
> binding"
>   and uses a similar object where the content is the SID of the  
> primary
>   flow. Achieves the same thing, and you can be sure there are no
>   collisions with nonces. Does the value need to be a random value? Or
>   could you perhaps re-use the QoS NSLP object since we have common  
> object
>   repository anyway? The concept in the QoS NSLP session binding is  
> that
>   the secondary session is valid as long as the primary session is.

Actually it is a good idea to use the SID of the primary flow as  
content for the NONCE object. Fixed.

For the shared object: I would like to keep two separate objects, as  
this proxy mechanism is quite new and probably needs to be refined in  
the future, i.e., good to have no dependency here.

>
> - Related to the above, p.48 (middle): if you have the "internal"
>   CREATE+NONCE session and also get the e2e CREATE session, do you run
>   both simultaneously? Or do you kill one of them? I guess you  
> can't kill
>   the EXT-session, since you need the forwarding at the NAT?  
> Perhaps this
>   needs some more description.

There is text on page 48 describing the possible way of tearing down  
the proxy session. The non-proxy CREATE session is still alive but  
can be also torn down by the data receiver (i.e. using NOTIFY).   
However, there is now a new NOTIFY reason to have a better handle to  
this:
'NATFW signaling session terminated' (0x05).
Added text about using this to CREATE.

>
> - p.49: "back to NI according [to] the situation"

Fixed.

>
> - p.49: "NSLP node and the of the policy rule."?

Fixed.

>
> - p.51: Do the route changes really work as you describe? This may  
> need
>   some thinking, and probably add text to the mobility draft.

Yes, route change works as defined. The handling is a bit different  
from the QoS NSLP but this is due the different signalling models used.
This will for sure need some text in the mobility draft (which I  
still owe...)

>
> - p.51: s/and sends it/and send it/

Fixed.

>
> - Whole Section 4: the text talks about error cases and mandating  
> "MUST"
>   to send various error messages? If you must always send error  
> messages,
>   isn't this a use case for DoS attacks? I guess some words about  
> when to
>   send error messages would be needed (rate limiting, etc.).

If a DoS attack is possible by sending error response something has  
already be gone wrong on the GIST level, isn't it?

It is also not possible to get some amplification as a single request  
message results in a single error response message. And the error  
response is anyhow sent back via the existing GIST messaging  
association.

Also, I'm quite uneasy to tell which error message should be sent and  
which not. This selection is quite tough.

>
> - p.57 (top of page): "Further version of this memo may allow other  
> values
>   for the 'sub_ports' field." I think suggestions like this should  
> not be
>   in a draft going to WGLC.

Hmm, right. Removed.

>
> - p.58-60: there are a lot of error codes. Should somewhere be  
> written how
>   and when these are used? Some of these are quite clear, but e.g.  I
>   don't understand Permanent failures 0x03, 0x05 and 0x06. Where would
>   these be used?

0x03 Unable to agree transport security with peer.
0x05 No NAT here.
are really not used in the document at all. They are some left-overs  
and have been removed.

0x06 No edge-device here.
is used in section Reserving External Addresses.


>
> - p.61, Section 4.2.7: where is this object used actually? text says
>   "possibly needed", sounds a bit wierd for a draft in WGLC. Is it  
> needed,

The "possibly needed" refers to the information carried in the  
object, as not all of the information is always needed but only  
sometimes (as highlighted in section Reservation message flow for DR  
behind NAT or firewall).

>   and where/when/why? Should this be also available for IPv6?

Nope. For IPv6 the IP address in the object is not meaningful, as  
IPv6 does not have NATs and therefore the rules for firewall only  
applies. This implies using the PC-MRM for signaling where the DTINFO  
address is anyway not used.

>
> - p.62, 3rd line: "according [to] these rules:"

Fixed.

>
> - p.64, Sections 4.3.1 and 4.3.2: what are these "(O)" and "(M)"?  
> Optional
>   and mandatory? Say it clearly.

Clearly stated in 2nd para in 4.3.

>
> - p.64, Section 4.3.2: point c) as use case for EXT: you lost me  
> here? Was
>   this presented earlier? Actually, in general about EXT, should it  
> always

Yes, this is in a bit hidden in the policy rule section. You can send  
around policy rules with action 'deny'. That is point c).
I could add references to the particular sections if this helps  
reading it?

>   have the proxy bit P=1? What happens if I send an EXT message  
> towards
>   the DS with P=0? Does the EXT reach the DS? What happens then?

DS generates an error response (see EXTERNAL section).

>
> - p.67: "In Section 5.1 we describe [how] the ..."

Fixed.

>
> - p.73: s/located to the/located at the/

Fixed.

Once again: Thanks a lot!

   Martin

stiemerling@netlab.nec.de

NEC Laboratories Europe - Network Research Division

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


--Apple-Mail-12--462122613
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
Hi Jukka,<div><br class=3D"webkit-block-placeholder"></div><div>Thanks =
for the review and more inline.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>=A0=A0Martin</div><div><br><=
div><div>Am 04.12.2007 um 23:06 schrieb Jukka MJ Manner:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Hi,</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">I have reviewed that draft. I don't have any major =
objections to the<span class=3D"Apple-converted-space">=A0</span></div><di=
v style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">document, just some miscellaneous comments and =
clarification requests.</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Here goes:</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">- p.6, =
bullet 1: at this point in the document, it is not clear to the<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>reader what the NSIS =
initiator/receiver are. Propose to use simpler<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>terminology at this early =
phase in the intro.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed. E.g., =
s/NSIS=A0initiator/initiator of the NSIS signaling</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- p.6, end of page: propose to clearly say wo sends =
which message, e.g.:</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">"CREATE message: send by the =
data sender for..."</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">"EXTERNAL message: used by data =
receiver to ..."</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Related comment: why abbreviate EXTERNAL to =
"EXT"?<span class=3D"Apple-converted-space">=A0</span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>* None of the other message are =
abbreviated</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>* EXTERNAL is as long a word as =
"RESPONSE" (both abbreviated?)</div></blockquote><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Suggest to drop the =
EXT-term</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Done and I have changed to =
EXTERNAL in all=A0occurrences,=A0</div><br><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Related =
to the above the document presents over and over again that<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">EXTERNAL =
is EXT ("EXTERNAL (EXT)") and is a bit inconsistent in when to<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">use =
EXTERNAL and when just EXT (both used here and =
there).</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed, as it is called =
EXTERNAL only now.</div><br><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">- p.7.: =
s/body of the document, covers/body of the document =
cover/</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- p.23: s/inSection/in =
Section/</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- p.27: "if the node runs _it_ garbage collection =
cycle."?<span =
class=3D"Apple-converted-space">=A0</span></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- p.27: "appropriate error of class 'Protocol error' =
(0x1)": 0x1 is<span class=3D"Apple-converted-space">=A0</span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0 =
</span>Informational, ox3 is protocol error.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- p.32: "is thus managed NSLP =
hop-by-hop"?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><div><br =
class=3D"webkit-block-placeholder"></div><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">- p.41: =
"session created by REA."?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- p.41: "using CREATE Section 3.7.1" &gt; "(see =
Section 3.7.1)"?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- p.43: "if the like to =
aggregate"?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- p.46, whole Section 3.7.6.1: should NR be actually =
DR? Including Figure<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 =
</span>18?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>I prefer to leave NR in =
the text, but have added the term DR to figure 18. This should make it =
clear.</div><br><blockquote type=3D"cite"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">- P.46-47, Section 3.7.6.1: I =
don't really get this operation at all.<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>Sounds a bit complex to have =
the EXT-session trigger a CREATE-session.<span =
class=3D"Apple-converted-space">=A0</span></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>That's the best way ensure =
faith sharing between both of them. The CREATE session should die =
together with the EXTERNAL-PROXY session.=A0</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>Maybe some more =
discussion/description is needed to open up the<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>scenario. Also, the =
NATFW_NONCE sounds a bit wierd, somehow. In the QoS<span =
class=3D"Apple-converted-space">=A0</span></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Added some text to =
actually describe the dependency between the sessions of EXTERNAL and =
CREATE.</div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>NSLP, we have the same =
functionality, but it is called "session binding"<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>and uses a similar object =
where the content is the SID of the primary<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>flow. Achieves the same =
thing, and you can be sure there are no<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>collisions with nonces. Does =
the value need to be a random value? Or<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>could you perhaps re-use the =
QoS NSLP object since we have common object<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>repository anyway? The =
concept in the QoS NSLP session binding is that<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>the secondary session is =
valid as long as the primary session is.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Actually it is a good idea =
to use the SID of the primary flow as content for the NONCE object. =
Fixed.=A0</div><div><br class=3D"webkit-block-placeholder"></div><div>For =
the shared object: I would like to keep two separate objects, as this =
proxy mechanism is quite new and probably needs to be refined in the =
future, i.e., good to have no=A0dependency=A0here.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- Related to the above, p.48 (middle): if you have =
the "internal"<span class=3D"Apple-converted-space">=A0</span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0 =
</span>CREATE+NONCE session and also get the e2e CREATE session, do you =
run<span class=3D"Apple-converted-space">=A0</span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0 =
</span>both simultaneously? Or do you kill one of them? I guess you =
can't kill<span class=3D"Apple-converted-space">=A0</span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0 </span>the =
EXT-session, since you need the forwarding at the NAT? Perhaps this<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>needs some more =
description.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>There is text on page 48 =
describing the possible way of tearing down the proxy session. The =
non-proxy CREATE session is still alive but can be also torn down by the =
data receiver (i.e. using NOTIFY). =A0However, there is now a new NOTIFY =
reason to have a better handle to this:</div><div>'NATFW signaling =
session terminated' (0x05).=A0</div><div>Added text about using this to =
CREATE.</div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">- p.49: "back =
to NI according [to] the situation"</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- p.49: "NSLP node and the of the policy =
rule."?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div>Fixed.=A0</div><div><br><blockquo=
te type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- p.51: Do the route changes really work as you =
describe? This may need<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>some thinking, and probably =
add text to the mobility draft.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Yes, route change works as =
defined. The handling is a bit different from the QoS NSLP but this is =
due the different signalling models used.=A0</div><div>This will for =
sure need some text in the mobility draft (which I still =
owe...)</div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">- p.51: s/and =
sends it/and send it/</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- Whole Section 4: the text talks about error cases =
and mandating "MUST"<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>to send various error =
messages? If you must always send error messages,<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>isn't this a use case for DoS =
attacks? I guess some words about when to<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>send error messages would be =
needed (rate limiting, etc.).</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>If a DoS attack is =
possible by sending error response something has already be gone wrong =
on the GIST level, isn't it?</div><div><br =
class=3D"webkit-block-placeholder"></div><div>It is also not possible to =
get some amplification as a single request message results in a single =
error response message. And the error response is anyhow sent back via =
the=A0existing=A0GIST messaging =
association.=A0</div><div><br></div><div>Also, I'm quite uneasy to tell =
which error message should be sent and which not. This selection is =
quite tough.=A0</div><br><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">- p.57 =
(top of page): "Further version of this memo may allow other values<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>for the 'sub_ports' field." I =
think suggestions like this should not be<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>in a draft going to =
WGLC.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Hmm, right. =
Removed.</div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">- p.58-60: =
there are a lot of error codes. Should somewhere be written how<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>and when these are used? Some =
of these are quite clear, but e.g.<span class=3D"Apple-converted-space">=A0=
 </span>I<span class=3D"Apple-converted-space">=A0</span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0 =
</span>don't understand Permanent failures 0x03, 0x05 and 0x06. Where =
would<span class=3D"Apple-converted-space">=A0</span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0 =
</span>these be used?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>0x03=A0Unable to agree =
transport security with peer.</div><div>0x05=A0No NAT =
here.</div><div>are really not used in the document at all. They are =
some left-overs and have been removed.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>0x06=A0No edge-device =
here.</div><div>is used in section=A0Reserving External =
Addresses.</div><div><br class=3D"webkit-block-placeholder"></div><div><br=
 class=3D"webkit-block-placeholder"></div><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">- p.61, =
Section 4.2.7: where is this object used actually? text says<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>"possibly needed", sounds a =
bit wierd for a draft in WGLC. Is it needed,<span =
class=3D"Apple-converted-space">=A0</span></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>The "possibly needed" =
refers to the information carried in the object, as not all of the =
information is always needed but only sometimes (as highlighted in =
section=A0Reservation message flow for DR behind NAT or =
firewall).</div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>and where/when/why? Should =
this be also available for IPv6?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Nope. For IPv6 the IP =
address in the object is not meaningful, as IPv6 does not have NATs and =
therefore the rules for firewall only applies. This implies using the =
PC-MRM for signaling where the DTINFO address is anyway not =
used.=A0</div><div><br =
class=3D"webkit-block-placeholder"></div><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">- p.62, =
3rd line: "according [to] these rules:"</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- p.64, Sections 4.3.1 and 4.3.2: what are these =
"(O)" and "(M)"? Optional<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>and mandatory? Say it =
clearly.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Clearly stated in 2nd para =
in 4.3.</div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">- p.64, =
Section 4.3.2: point c) as use case for EXT: you lost me here? Was<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>this presented earlier? =
Actually, in general about EXT, should it always<span =
class=3D"Apple-converted-space">=A0</span></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Yes, this is in a bit =
hidden in the policy rule section. You can send around policy rules with =
action 'deny'. That is point c).=A0</div><div>I could add references to =
the particular sections if this helps reading it?</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>have the proxy bit P=3D1? =
What happens if I send an EXT message towards<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>the DS with P=3D0? Does the =
EXT reach the DS? What happens then?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>DS generates an error =
response (see EXTERNAL section).=A0</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- p.67: "In Section 5.1 we describe [how] the =
..."</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- p.73: s/located to the/located at =
the/</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Once again: Thanks a =
lot!</div><div><br></div><div>=A0=A0Martin</div><div><br =
class=3D"webkit-block-placeholder"></div></div><div> <span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: 'Lucida Grande'; font-size: 12px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div><a =
href=3D"mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</a></d=
iv><div><br></div><div><div>NEC Laboratories Europe - Network Research =
Division</div><div><br class=3D"webkit-block-placeholder"></div><div>NEC =
Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014</div></div></span> =
</div><br></div></body></html>=

--Apple-Mail-12--462122613--



--===============0083494804==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0083494804==--





From nsis-bounces@ietf.org Thu Jan 24 09:13:52 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JI2px-0008Ea-OS; Thu, 24 Jan 2008 09:13:49 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JI2pv-0008EK-Nl
	for nsis-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 09:13:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JI2pv-0008EC-Dm
	for nsis@ietf.org; Thu, 24 Jan 2008 09:13:47 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JI2pt-0005XW-8x
	for nsis@ietf.org; Thu, 24 Jan 2008 09:13:47 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id BC91728000455;
	Thu, 24 Jan 2008 15:13:44 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6jp4qM61uTEJ; Thu, 24 Jan 2008 15:13:44 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 9720F28000356;
	Thu, 24 Jan 2008 15:13:34 +0100 (CET)
Received: from [10.1.1.109] ([10.1.1.109]) by mx1.office over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 24 Jan 2008 15:13:34 +0100
In-Reply-To: <20071211092834.552A.SANDA.TAKAKO@jp.panasonic.com>
References: <57BCC14C-53FD-4B9C-8EEE-C2D5D78B0B1F@netlab.nec.de>
	<20071211092834.552A.SANDA.TAKAKO@jp.panasonic.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <0DD9706E-33C4-4A86-8ADA-924A8D2E1552@netlab.nec.de>
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Subject: Re: [NSIS] WGLC: draft-ietf-nsis-nslp-natfw-16.txt
Date: Thu, 24 Jan 2008 15:13:33 +0100
To: Takako Sanda <sanda.takako@jp.panasonic.com>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 24 Jan 2008 14:13:34.0357 (UTC)
	FILETIME=[4E19B450:01C85E93]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dd7e0c3fd18d19cffdd4de99a114001d
Cc: nsis <nsis@ietf.org>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0236877430=="
Errors-To: nsis-bounces@ietf.org


--===============0236877430==
Content-Type: multipart/alternative; boundary=Apple-Mail-15--461485625


--Apple-Mail-15--461485625
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hi Takako,

Am 11.12.2007 um 01:49 schrieb Takako Sanda:
e
> Hi all,
>
> Regarding NAT traversal, NSIS Mobility Applicability draft also has  
> two
> open issues (as shown below). But I am not sure Mobility draft is  
> proper
> place to handle these issues. I would like to ask whether these two
> issues can be discussed in NATFW draft.
>
> Issue 1:
> When MN moves, IP address and routing are changed.  In this case, new
> NAT/FW pinhole need to be opened and old one should be torn. When and
> how should NSIS tear old pinhole?
>
> (For this issue, some comments were already made that the old pinhole
> should be torn by time out, and this prefer to be mentioned in  
> Mobility
> draft.)

Preferably this would be described in the mobility draft, as it is  
really a mobility issue.

>
> Issue 2: In mobility scenario, it is possible that MN attaches to
> private network. But MN cannot know if the NAT is NSIS aware or not.
> Therefore should it be mandatory that MN sets S-flag when it detect
> attaching a private network?

That is a GIST issue and Section 7.2.1. Legacy NAT Handling of the  
GIST draft recommends S=1 to support legacy NAT detection.

   Martin


>
> cheers,
> Takako
>
>
>
>
>
> On Fri, 23 Nov 2007 13:44:20 +0100
> Martin Stiemerling <stiemerling@netlab.nec.de> wrote:
>
>> [writing as WG chair]
>>
>> Dear all,
>>
>> The authors believe that the NATFW NSLP
>> (draft-ietf-nsis-nslp-natfw-16.txt) is ready for WGLC.
>>
>> The WGLC starts today and will run until December 14th.
>>
>> Please review the draft, and comment if you feel that this draft
>> is ready to be sent to the IESG.  A simple mail saying that the
>> draft is ready for publication would be great.
>>
>> Of course, if you read the draft and find open issues, then please
>> send a summary of your issue with the current draft.
>>
>> Thanks,
>>
>>    John and Martin
>>
>> stiemerling@netlab.nec.de
>> NEC Laboratories Europe - Network Research Division
>>
>> NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road,
>> London W3 6BL | Registered in England 2832014
>>
>>
>

stiemerling@netlab.nec.de

NEC Laboratories Europe - Network Research Division

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


--Apple-Mail-15--461485625
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
Hi Takako,=A0<div><br><div><div>Am 11.12.2007 um 01:49 schrieb Takako =
Sanda:</div>e<br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Hi all,</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Regarding NAT traversal, NSIS Mobility Applicability draft also has =
two</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">open issues (as shown below). =
But I am not sure Mobility draft is proper</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">place to =
handle these issues. I would like to ask whether these two</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">issues can be discussed in NATFW draft.</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Issue =
1:</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; ">When MN moves, IP address and routing are =
changed.<span class=3D"Apple-converted-space">=A0 </span>In this case, =
new</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">NAT/FW pinhole need to be opened =
and old one should be torn. When and</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">how should =
NSIS tear old pinhole?</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">(For this issue, some comments =
were already made that the old pinhole</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">should =
be torn by time out, and this prefer to be mentioned in =
Mobility</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; =
">draft.)</div></blockquote><div><br></div><div>Preferably this would be =
described in the mobility draft, as it is really a mobility =
issue.=A0</div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Issue 2: In =
mobility scenario, it is possible that MN attaches to</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">private network. But MN cannot know if the NAT is =
NSIS aware or not.</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">Therefore should it be =
mandatory that MN sets S-flag when it detect</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">attaching a private =
network?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>That is a GIST issue and =
Section=A07.2.1. Legacy NAT Handling of the GIST draft recommends S=3D1 =
to support legacy NAT detection.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>=A0=A0Martin</div><div><br =
class=3D"webkit-block-placeholder"></div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">cheers,</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Takako</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">On Fri, 23 Nov 2007 13:44:20 +0100</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Martin Stiemerling &lt;<a =
href=3D"mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</a>&gt=
; wrote:</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div> =
<blockquote type=3D"cite"><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">[writing as WG =
chair]</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Dear all,</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">The authors believe that the =
NATFW NSLP</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; =
">(draft-ietf-nsis-nslp-natfw-16.txt) is ready for WGLC.</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The WGLC =
starts today and will run until December 14th.</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Please =
review the draft, and comment if you feel that this draft</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">is ready to be sent to the IESG.<span =
class=3D"Apple-converted-space">=A0 </span>A simple mail saying that =
the</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">draft is ready for publication =
would be great.</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Of course, if you read the draft and find open =
issues, then please</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">send a summary of your =
issue with the current draft.</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Thanks,</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>John and Martin</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a =
href=3D"mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</a></d=
iv><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">NEC Laboratories Europe - Network Research =
Division</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">NEC Europe Limited | Registered Office: NEC House, 1 =
Victoria Road, <span class=3D"Apple-converted-space">=A0</span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">London W3 6BL | Registered in England =
2832014</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div> </blockquote><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div> =
</blockquote></div><br><div> <span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Lucida Grande'; font-size: 12px; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div><a =
href=3D"mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</a></d=
iv><div><br></div><div><div>NEC Laboratories Europe - Network Research =
Division</div><div><br class=3D"webkit-block-placeholder"></div><div>NEC =
Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014</div></div></span> =
</div><br></div></body></html>=

--Apple-Mail-15--461485625--



--===============0236877430==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0236877430==--





From nsis-bounces@ietf.org Thu Jan 24 10:07:26 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JI3fp-0004bv-17; Thu, 24 Jan 2008 10:07:25 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JI3fn-0004bp-JS
	for nsis-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 10:07:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JI3fn-0004bh-9a
	for nsis@ietf.org; Thu, 24 Jan 2008 10:07:23 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JI3fl-0006YJ-ES
	for nsis@ietf.org; Thu, 24 Jan 2008 10:07:23 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 0B0A128000356;
	Thu, 24 Jan 2008 16:07:21 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id X89Fu-tUjKEE; Thu, 24 Jan 2008 16:07:20 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id D73722800034F;
	Thu, 24 Jan 2008 16:07:10 +0100 (CET)
Received: from [10.1.1.109] ([10.1.1.109]) by mx1.office over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 24 Jan 2008 16:07:10 +0100
In-Reply-To: <475E7303.3080800@cs.uni-goettingen.de>
References: <57BCC14C-53FD-4B9C-8EEE-C2D5D78B0B1F@netlab.nec.de>
	<475E7303.3080800@cs.uni-goettingen.de>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <17167872-3714-4233-B113-92BC1933E5F7@netlab.nec.de>
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Subject: Re: [NSIS] WGLC: draft-ietf-nsis-nslp-natfw-16.txt
Date: Thu, 24 Jan 2008 16:07:09 +0100
To: Niklas Steinleitner <steinleitner@cs.uni-goettingen.de>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 24 Jan 2008 15:07:10.0595 (UTC)
	FILETIME=[CB20AD30:01C85E9A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e06437eb72f6703f11713d345be8298a
Cc: nsis <nsis@ietf.org>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1522189442=="
Errors-To: nsis-bounces@ietf.org


--===============1522189442==
Content-Type: multipart/alternative; boundary=Apple-Mail-16--458269837


--Apple-Mail-16--458269837
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed


Am 11.12.2007 um 12:22 schrieb Niklas Steinleitner:

> Hi Martin, all,
>
> i have reviewed the NATFW NSLP draft. Overall i think the draft is  
> in a good shape.
>
> My three major comments:
> p24: Redraw the picture! Add administrative domains or point out  
> with node
Done.

> belongs to which network! Also rewrite the first paragraph! Use a  
> easier example! This section indicates (at least to me) the usage  
> of the proxy mode in a way which is not supported by NATFW!
Para rewritten a bit. No idea why this is not supported by the NATFW  
NSLP...?

> p26/section 3.2.3: Why do you have this section within the draft?  
> The listed states are not enough to implement the NATFW NSLP and  
> may confuse reviewers/implementers. You could point to the  
> statemachine draft! If you want to have this section inside the  
> draft, you should update it. What is the "Dead" state good for?  
> Such a session has to be deleted directly and not "... and the  
> NATFW NSLP signaling session can be deleted."

The listed state are for sure not enough for a real implementation,  
but they describe the conceptual states. The state machine draft is  
not a WG item.
> regarding section 3.7.2: this section is a little bit confusing!  
> Even with knowledge about the NATFW NSLP it is hard to follow.  
> Maybe you should re-structure it a little bit, e.g. creating  
> several sub-sections. You should also clearly point out that EXT  
> can also be used to install pinholes in FWs (and not only deny  
> rules as described later, if i don't understand this wrong (see  
> below)).

This section has been rewritten some times already and it seems that  
it never ever gets to a point where it is understandable for  
everybody.  I do see the point, but I don't like to change it again,  
as we have cycled through the section already several times.
This is not really an argument, but if you have a real proposal send it!
>
> Further comments:
> p2/p4: If you introduce NAT, you should do the same for FW
The term firewall and NAT are well-known and also again defined in  
the terminology section. This should be enough of definition.

> p8/p10: you introduce the terminology "middlebox" twice, in section  
> 1.2. and section 1.3

Yes right. Removed it from 1.2 and put in front of 1.3. Fixed.

> p11: meaning that there is a middlebox on the => meaning that there  
> is at least one middlebox on the
Fixed.

> p22, first paragraph: (check local policies for authorization and  
> authentication, possibly create policy rules) that is not right,  
> the NF only notice the policy rules
> p22, third paragraph: the NF installs the policy rule when  
> receiving a success RESPONSE msg
Yes and no. Technically you are right, but I believe it is too early  
in the document to introduce the technical difference between  
remembered/reserved/installed policy rule.

> p22, fourth paragraph: Ni => NI

Fixed.
> p27: 'Protocol error' (0x1) => (0x3)
Fixed.

> p29/p30: many recurrences here: Requested signaling session  
> lifetime is too big, Requested signaling session lifetime is too  
> small, with codes, the same on page 30
Not nice but required. This part is anyhow question in my mail sent  
Jan 24 with subject "Lifetime error messages".

> p32: section 3.7:  ... how to create NATFW NSLP signaling sessions,  
> maintain them, and how to reserve addresses. => and delete
Wouldn't be a sentence anymore w/o 'and'?

> p34: NSLP forwarder: what happened if the NF can not install the  
> pinhole? e.g. it is already installed
Added text about generating error response with  0x04: Requested  
policy rule denied due to policy conflict.
>
> looks like you forgot this case, there is also node error code for  
> this case on page 58.

See above. Fixed.
> p40:  ... an error RESPONSE of class 'Protocol error' (0x3) ... =>  
> of class signaling session failure (0x6)

protocol error is right.

>
> p40: "The policy rule is remembered, but not activated, if the  
> action in the NATFW_EFI object is set to 'allow'." Why? In general,  
> i don't understand the "Firewall" paragraph.

The rule is just remembered and not activated, as this is just for  
telling the firewall about future incoming CREATE requests. This rule  
is activated by a later sent CREATE request.
See also the terminology section about the difference between  
remembered policy rules.

> p41: "Reservations with action 'allow' made with EXT MUST be  
> enabled by a subsequent CREATE message." What happens if the  
> pinhole isn't use for reservation of an external address or a NAT- 
> binding? In this case no CREATE msg will follow.
> or is this in general not allow within the NATFW NSLP? The next  
> sentence indicates that:
> "The only function of EXT is to ensure that subsequent CREATE  
> messages traveling towards the NR will be forwarded across the  
> public-private boundary towards the DR."
> One earlier version of the NATFW NSLP supports this with the use of  
> U-CREATE. Or is this completely remove?

There is now the proxy mode operation for this.
>
> p41: ...created by REA. => ... created by EXT.
Fixed.

> p42: "The lifetime extension of a NATFW NSLP signaling session is  
> calculated as current local time plus proposed lifetime value",  
> really local time plus proposed? This would increase the lifetime  
> step by step as the local lifetime is always >0!
Good point the wording is misleading...
New text: "The new (extended) lifetime of..."
> p44: "'NATFW node is going down soon' (0x03) The NI and other NFs  
> should be prepared for a service interruption at any time."
> What is this good for????
This is a soft warning to others, i.e., the NI can change the refresh  
interval to a shorter period. This allows detecting route changes  
earlier. Sometimes nodes do have some knowledge about maintenance or  
so and this message could be sent if the operator is about to halt  
the device.

> p48/49, section 3.7.6.2: you should make clear where are the  
> differences to the EXT msg.
Isn't this clear by the division of the section into "proxy for  
sender" and "proxy for receiver"?

> p52: ... of this memo => ...of this memo.

fixed.
> p56: ... of class 'Signaling session error' (0x6) with ... => ...  
> of class 'Signaling session failure' (0x6) with ...
fixed.

> p58: you forgot 0x04 (see 3.7.5) 'NATFW signaling session lifetime  
> expired'
Fixed.

>
> p59(and whole doc) => signaling session failures => signaling  
> session failure (as for the other classes).

Fixed.
> p62: The fields MUST be interpreted according these rules: => The  
> fields MUST be interpreted according to these rules:
Fixed.

> p62: with response code 'Mandatory object missing' (0x02) MUST =>  
> (0x04)
Fixed.

> p76: Open issues. Should this be part of a WGLC document?
Nope! :)
Removed.

Thanks again!

   Martin

stiemerling@netlab.nec.de

NEC Laboratories Europe - Network Research Division

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


--Apple-Mail-16--458269837
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<br><div><div>Am 11.12.2007 um 12:22 schrieb Niklas =
Steinleitner:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">  Hi Martin, all,<br> <br> i have reviewed the NATFW NSLP =
draft. Overall i think the draft is in a good shape.<br> <br> My three =
major comments:<br> <ul>  <li>p24: Redraw the picture! Add =
administrative domains or point out with node =
</li></ul></blockquote><div>Done.</div><br><blockquote =
type=3D"cite"><ul><li>belongs to which network! Also rewrite the first =
paragraph! Use a easier example! This section indicates (at least to me) =
the usage of the proxy mode in a way which is not supported by =
NATFW!</li></ul></blockquote><div>Para rewritten a bit. No idea why this =
is not supported by the NATFW NSLP...?</div><div><br =
class=3D"webkit-block-placeholder"></div><blockquote type=3D"cite"><ul>  =
<li>p26/section 3.2.3: Why do you have this section within the draft? =
The listed states are not enough to implement the NATFW NSLP and may =
confuse reviewers/implementers. You could point to the statemachine =
draft! If you want to have this section inside the draft, you should =
update it. What is the "Dead" state good for? Such a session has to be =
deleted directly and not "... and the NATFW NSLP signaling session can =
be deleted."</li></ul></blockquote><div><br =
class=3D"webkit-block-placeholder"></div>The listed state are for sure =
not enough for a real implementation, but they describe the conceptual =
states. The state machine draft is not a WG item.<br><blockquote =
type=3D"cite"><ul>  <li>regarding section 3.7.2: this section is a =
little bit confusing! Even with knowledge about the NATFW NSLP it is =
hard to follow. Maybe you should re-structure it a little bit, e.g. =
creating several sub-sections. You should also clearly point out that =
EXT can also be used to install pinholes in FWs (and not only deny rules =
as described later, if i don't understand this wrong (see =
below)).</li></ul></blockquote><div><br =
class=3D"webkit-block-placeholder"></div>This section has been rewritten =
some times already and it seems that it never ever gets to a point where =
it is understandable for everybody. =A0I do see the point, but I don't =
like to change it again, as we have cycled through the section already =
several times.=A0</div><div>This is not really an argument, but if you =
have a real proposal send it!=A0<br><blockquote type=3D"cite"><ul><li><br>=
  </li> </ul> Further comments:<br> <ul>  <li>p2/p4: If you introduce =
NAT, you should do the same for FW</li></ul></blockquote><div>The term =
firewall and NAT are well-known and also again defined in the =
terminology section. This should be enough of =
definition.</div><br><blockquote type=3D"cite"><ul>  <li>p8/p10: you =
introduce the terminology "middlebox" twice, in section 1.2. and section =
1.3</li></ul></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Yes right. Removed it from =
1.2 and put in front of 1.3. Fixed.</div><br><blockquote =
type=3D"cite"><ul>  <li>p11: meaning that there is a middlebox on the =
=3D&gt; meaning that there is <u>at least one</u> middlebox on =
the</li></ul></blockquote><div>Fixed.</div><br><blockquote =
type=3D"cite"><ul>  <li>p22, first paragraph: (check local policies for =
authorization and authentication, possibly create policy rules) that is =
not right, the NF only notice the policy rules</li>  <li>p22, third =
paragraph: the NF installs the policy rule when receiving a success =
RESPONSE msg</li></ul></blockquote><div>Yes and no. Technically you are =
right, but I believe it is too early in the document to introduce the =
technical difference between remembered/reserved/installed policy =
rule.=A0</div><div><br></div><blockquote type=3D"cite"><ul>  <li>p22, =
fourth paragraph: Ni =3D&gt; NI</li></ul></blockquote><div><br =
class=3D"webkit-block-placeholder"></div>Fixed.<br><blockquote =
type=3D"cite"><ul>  <li>p27: 'Protocol error' (0x1) =3D&gt; =
(0x3)</li></ul></blockquote><div>Fixed.</div><br><blockquote =
type=3D"cite"><ul>  <li>p29/p30: many recurrences here: Requested =
signaling session lifetime is too big, Requested signaling session =
lifetime is too small, with codes, the same on page =
30</li></ul></blockquote><div>Not nice but required. This part is anyhow =
question in my mail sent Jan 24 with subject "Lifetime error =
messages".</div><br><blockquote type=3D"cite"><ul>  <li>p32: section =
3.7:=A0 ... how to create NATFW NSLP signaling sessions, maintain them, =
and how to reserve addresses. =3D&gt; and =
delete</li></ul></blockquote><div>Wouldn't be a sentence anymore w/o =
'and'?</div><br><blockquote type=3D"cite"><ul>  <li>p34: NSLP forwarder: =
what happened if the NF can not install the pinhole? e.g. it is already =
installed</li></ul></blockquote><div>Added text about generating error =
response with=A0=A00x04: Requested policy rule denied due to policy =
conflict.</div><blockquote type=3D"cite"><ul><li><br> looks like you =
forgot this case, there is also node error code for this case on page =
58.</li></ul></blockquote><div><br =
class=3D"webkit-block-placeholder"></div>See above. =
Fixed.<br><blockquote type=3D"cite"><ul>  <li>p40:=A0 ... an error =
RESPONSE of class 'Protocol error' (0x3) ... =3D&gt; of class signaling =
session failure (0x6)</li></ul></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>protocol error is =
right.</div><br><blockquote type=3D"cite"><ul><li><br>  </li>  <li>p40: =
"The policy rule is remembered, but not activated, if the action in the =
NATFW_EFI object is set to 'allow'." Why? In general, i don't understand =
the "Firewall" paragraph.</li></ul></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>The rule is just =
remembered and not activated, as this is just for telling the firewall =
about future incoming CREATE requests. This rule is activated by a later =
sent CREATE request.</div><div>See also the terminology section about =
the difference between remembered policy rules.</div><br><blockquote =
type=3D"cite"><ul>  <li>p41: "Reservations with action 'allow' made with =
EXT MUST be enabled by a subsequent CREATE message." What happens if the =
pinhole isn't use for reservation of an external address or a =
NAT-binding? In this case no CREATE msg will follow.<br>  </li>  <ul>    =
<li>or is this in general not allow within the NATFW NSLP? The next =
sentence indicates that:<br>    </li>    <li>"The only function of EXT =
is to ensure that subsequent CREATE messages traveling towards the NR =
will be forwarded across the public-private boundary towards the =
DR."<br>    </li>  </ul>  <ul>    <li>One earlier version of the NATFW =
NSLP supports this with the use of U-CREATE. Or is this completely =
remove?</li></ul></ul></blockquote><div><br =
class=3D"webkit-block-placeholder"></div>There is now the proxy mode =
operation for this.<br><blockquote type=3D"cite"><ul><ul><li><br>    =
</li>  </ul>  <li>p41: ...created by REA. =3D&gt; ... created by =
EXT.</li></ul></blockquote><div>Fixed.</div><br><blockquote =
type=3D"cite"><ul>  <li>p42: "The lifetime extension of a NATFW NSLP =
signaling session is calculated as current local time plus proposed =
lifetime value", really local time <u><b>plus </b></u>proposed? This =
would increase the lifetime step by step as the local lifetime is always =
&gt;0!</li></ul></blockquote><div>Good point the wording is =
misleading...</div><div>New text: "The new (extended) lifetime =
of..."</div><blockquote type=3D"cite"><ul>  <li>p44: "'NATFW node is =
going down soon' (0x03) The NI and other NFs should be prepared for a =
service interruption at any time."<br> What is this good =
for????</li></ul></blockquote><div>This is a soft warning to others, =
i.e., the NI can change the refresh interval to a shorter period. This =
allows detecting route changes earlier. Sometimes nodes do have some =
knowledge about maintenance or so and this message could be sent if the =
operator is about to halt the device.=A0</div><br><blockquote =
type=3D"cite"><ul>  <li>p48/49, section 3.7.6.2: you should make clear =
where are the differences to the EXT =
msg.</li></ul></blockquote><div>Isn't this clear by the division of the =
section into "proxy for sender" and "proxy for =
receiver"?</div><br><blockquote type=3D"cite"><ul>  <li>p52: ... of this =
memo =3D&gt; ...of this memo.</li></ul></blockquote><div><br =
class=3D"webkit-block-placeholder"></div>fixed.<br><blockquote =
type=3D"cite"><ul>  <li>p56: ... of class 'Signaling session error' =
(0x6) with ... =3D&gt; ... of class 'Signaling session failure' (0x6) =
with ...</li></ul></blockquote><div>fixed.</div><br><blockquote =
type=3D"cite"><ul>  <li>p58: you forgot 0x04 (see 3.7.5) 'NATFW =
signaling session lifetime =
expired'</li></ul></blockquote><div>Fixed.</div><br><blockquote =
type=3D"cite"><ul><li><br>  </li>  <li>p59(and whole doc) =3D&gt; =
signaling session failures =3D&gt; signaling session failure (as for the =
other classes).</li></ul></blockquote><div><br =
class=3D"webkit-block-placeholder"></div>Fixed.<br><blockquote =
type=3D"cite"><ul>  <li>p62: The fields MUST be interpreted according =
these rules: =3D&gt; The fields MUST be interpreted according <u><b>to =
</b></u>these =
rules:</li></ul></blockquote>Fixed.</div><div><br><blockquote =
type=3D"cite"><ul>  <li>p62: with response code 'Mandatory object =
missing' (0x02) MUST =3D&gt; =
(0x04)</li></ul></blockquote><div>Fixed.</div><br><blockquote =
type=3D"cite"><ul>  <li>p76: Open issues. Should this be part of a WGLC =
document?</li></ul></blockquote><div>Nope! =
:)</div><div>Removed.</div></div><div><br =
class=3D"webkit-block-placeholder"></div>Thanks again!<div><br =
class=3D"webkit-block-placeholder"></div><div>=A0=A0Martin</div><div><br><=
div> <span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-size: =
12px; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
auto; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div><a =
href=3D"mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</a></d=
iv><div><br></div><div><div>NEC Laboratories Europe - Network Research =
Division</div><div><br class=3D"webkit-block-placeholder"></div><div>NEC =
Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014</div></div></span> =
</div><br></div></body></html>=

--Apple-Mail-16--458269837--



--===============1522189442==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1522189442==--





From nsis-bounces@ietf.org Thu Jan 24 10:24:38 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JI3wT-00007w-7f; Thu, 24 Jan 2008 10:24:37 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JI3wR-0008SE-9h
	for nsis-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 10:24:35 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JI3wQ-0008PP-R7
	for nsis@ietf.org; Thu, 24 Jan 2008 10:24:34 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JI3wP-0007w8-8A
	for nsis@ietf.org; Thu, 24 Jan 2008 10:24:34 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id BDAA428000623;
	Thu, 24 Jan 2008 16:24:32 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fZhI7wymhzee; Thu, 24 Jan 2008 16:24:32 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id A034528000459;
	Thu, 24 Jan 2008 16:24:22 +0100 (CET)
Received: from [10.1.1.109] ([10.1.1.109]) by mx1.office over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 24 Jan 2008 16:24:22 +0100
In-Reply-To: <Pine.LNX.4.64.0712130151320.3636@sbz-32.cs.Helsinki.FI>
References: <57BCC14C-53FD-4B9C-8EEE-C2D5D78B0B1F@netlab.nec.de>
	<Pine.LNX.4.64.0712130151320.3636@sbz-32.cs.Helsinki.FI>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <65BB5B95-FBB4-4124-AA97-3562002CCAAA@netlab.nec.de>
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Subject: Re: [NSIS] WGLC: draft-ietf-nsis-nslp-natfw-16.txt
Date: Thu, 24 Jan 2008 16:24:21 +0100
To: Lauri J T Liuhto <lliuhto@cs.helsinki.fi>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 24 Jan 2008 15:24:22.0560 (UTC)
	FILETIME=[323A0A00:01C85E9D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 85e99493ec37f9acef29c7843dbf2e68
Cc: nsis <nsis@ietf.org>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1225577091=="
Errors-To: nsis-bounces@ietf.org


--===============1225577091==
Content-Type: multipart/alternative; boundary=Apple-Mail-17--457238117


--Apple-Mail-17--457238117
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hi Lauri,

Am 13.12.2007 um 01:08 schrieb Lauri J T Liuhto:

> On Fri, 23 Nov 2007, Martin Stiemerling wrote:
>> The authors believe that the NATFW NSLP
>> (draft-ietf-nsis-nslp-natfw-16.txt) is ready for WGLC.
>> The WGLC starts today and will run until December 14th.
>
>  Hi,
>
>  I have read the document, and I did not find any big issues, mainly
> just some editorial things. I did not repeat findings already
> provided by Jukka or Niklas.
>
>  Some parts of the text, mainly Section 3 (Protocol Description), was
> such, that I can not be sure whether I understood it completely. The
> text itself was quite easy to read, but I think those who have
> implemented this protocol can say more accurately how well the  
> protocol
> actually is described.
>
>  To make it short: I think the specification is in quite nice  
> state, and
> needs just some editorial fixes.

Thanks! :)

>
> Here are my comments on the draft:
>
>  * At page 11, line 571: 'routeable' --> 'routable' (?)

Fixed.

>
>  * Examples in Section 2 use mainly 'MB' in figures to represent NAT
>    and/or FW nodes. However, I think the use is not always
>    consistent. For example, in the figure 2 'FW' is used (and I think
>    it is ok, because the text explicitly states that this example is
>    about FW-only cases), but figure 9 in section 2.8 has 'MB's
>    instead. If those middle boxes in scenario 2.8 may be also NATs, I
>    think it would be nice to have it in text. If those middle boxes
>    are always firewalls as I think the text states, then the figure
>    should be changed.
>
>    However, I think that the text is clear enough already, and the
>    easy fix would be to change the 'FW' boxes to 'MB' boxes in the
>    figure 2 :)

2.8 and 2.7 have a subtle difference and it is better to change MB to  
FW in figure 9.

>
>  * Section 3.1 Policy Rules, first paragraph:
>
>  "For firewalls the policy rule usually consists of a 5-tuple, source/
>   destination addresses, transport protocol, and source/destination
>   port numbers, plus an action, such as allow or deny."
>
>   At least before reading the rest of the document, the word 'usually'
>   seems a bit odd here. Do real alternative policy rules that do not
>   contain the 5-tuple and action exist?
>
>   I also think this sentence is not too clear, some kind of
>   reformatting would be nice. For example, something like this (still
>   having the word 'usually'):
>
>  "For firewalls the policy rule usually consists of a 5-tuple and an
>   action such as allow or deny. The information contained in the tuple
>   includes source/destination addresses, transport protocol and
>   source/destination port numbers."

This reads better! Replaced it.

>
>  * In addition to comments Niklas already gave on figure 11 on page
>    24, I want to add that the figure and its legend do not
>    match. There is no MB2 in the figure, and NF is present in the
>    legend only in the text. As Niklas, I also think that it would be
>    good to point out which node belongs to which network.

Fixed.

>
>  * Page 28, last bullet:
>   "the lease time of the NI's IP address.  The chosen NATFW NSLP
>    signaling session lifetime must be larger than the lease time,
>    otherwise the IP address can be re-assigned to a different node.
>    This node may receive unwanted traffic, although it never has
>    requested a NAT/firewall configuration, which might be an issue in
>    mobile environments.
>
>    I just can not get the idea :) Should it be 'must be smaller than
>    the lease time' ? If not, then I think some more text is needed.

Yep, you're right, it must be smaller. I also bumped in this when  
reading. Fixed.

>
>  * Page 45, middle bullet:
>    "and outbound messages MUST be forwarded further inbound."
>    ->
>    "and outbound messages MUST be forwarded further outbound." ?

Fixed to outbound.

>
>   * Table 1 on page 50, the last row, capitalization:
>     left column: "IPsec SPI", right column: "ipsec-SPI"

That is intentionally, as the NATFW NSLP uses IPsec SPI as name and  
GIST uses ipsec-SPI.

Thanks a lot,

   Martin

stiemerling@netlab.nec.de

NEC Laboratories Europe - Network Research Division

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


--Apple-Mail-17--457238117
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
Hi=A0Lauri,<div><br><div><div><div>Am 13.12.2007 um 01:08 schrieb Lauri =
J T Liuhto:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">On Fri, 23 Nov 2007, Martin =
Stiemerling wrote:</div> <blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">The authors believe that the NATFW NSLP</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">(draft-ietf-nsis-nslp-natfw-16.txt) is ready for =
WGLC.</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">The WGLC starts today and will =
run until December 14th.</div> </blockquote><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0</span>Hi,<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0</span>I have read the document, and =
I did not find any big issues, mainly<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">just =
some editorial things. I did not repeat findings already<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">provided =
by Jukka or Niklas.</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0</span>Some parts of the text, mainly =
Section 3 (Protocol Description), was<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">such, =
that I can not be sure whether I understood it completely. The<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">text =
itself was quite easy to read, but I think those who have<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">implemented this protocol can say more accurately how well the =
protocol<span class=3D"Apple-converted-space">=A0</span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">actually is described.<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0</span>To make it short: I think the =
specification is in quite nice state, and<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">needs =
just some editorial fixes.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Thanks! =
:)</div><br><blockquote type=3D"cite"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Here are my comments on the =
draft:</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0</span>* At =
page 11, line 571: 'routeable' --&gt; 'routable' =
(?)</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0</span>* =
Examples in Section 2 use mainly 'MB' in figures to represent =
NAT</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>and/or FW nodes. However, =
I think the use is not always</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>consistent. For example, =
in the figure 2 'FW' is used (and I think</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>it is ok, because the text =
explicitly states that this example is</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>about FW-only cases), but =
figure 9 in section 2.8 has 'MB's</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>instead. If those middle =
boxes in scenario 2.8 may be also NATs, I</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>think it would be nice to =
have it in text. If those middle boxes</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>are always firewalls as I =
think the text states, then the figure</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>should be =
changed.</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0=A0 =
</span>However, I think that the text is clear enough already, and =
the</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>easy fix would be to =
change the 'FW' boxes to 'MB' boxes in the<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>figure 2 =
:)</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>2.8 and 2.7 have a subtle =
difference and it is better to change MB to FW in figure =
9.</div><br><blockquote type=3D"cite"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0</span>* Section 3.1 Policy Rules, =
first paragraph:</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0</span>"For =
firewalls the policy rule usually consists of a 5-tuple, =
source/</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>destination addresses, =
transport protocol, and source/destination</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>port numbers, plus an action, =
such as allow or deny."</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>At least before reading the =
rest of the document, the word 'usually'</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>seems a bit odd here. Do real =
alternative policy rules that do not</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>contain the 5-tuple and =
action exist?</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0 </span>I =
also think this sentence is not too clear, some kind of</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0 =
</span>reformatting would be nice. For example, something like this =
(still</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>having the word =
'usually'):</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0</span>"For =
firewalls the policy rule usually consists of a 5-tuple and an</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0 =
</span>action such as allow or deny. The information contained in the =
tuple</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>includes source/destination =
addresses, transport protocol and</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>source/destination port =
numbers."</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>This reads better! =
Replaced it.</div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0</span>* In addition to comments =
Niklas already gave on figure 11 on page</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>24, I want to add that the =
figure and its legend do not</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>match. There is no MB2 in =
the figure, and NF is present in the</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>legend only in the text. =
As Niklas, I also think that it would be</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>good to point out which =
node belongs to which network.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0</span>* =
Page 28, last bullet:</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>"the lease time of the NI's =
IP address.<span class=3D"Apple-converted-space">=A0 </span>The chosen =
NATFW NSLP</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>signaling session lifetime =
must be larger than the lease time,</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>otherwise the IP address =
can be re-assigned to a different node.</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>This node may receive =
unwanted traffic, although it never has</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>requested a NAT/firewall =
configuration, which might be an issue in</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>mobile =
environments.</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0=A0 =
</span>I just can not get the idea :) Should it be 'must be smaller =
than</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>the lease time' ? If not, =
then I think some more text is needed.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Yep, you're right, it must =
be smaller. I also bumped in this when reading. =
Fixed.</div><br><blockquote type=3D"cite"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0</span>* Page 45, middle =
bullet:</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>"and outbound messages =
MUST be forwarded further inbound."<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>-&gt;</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0=A0 =
</span>"and outbound messages MUST be forwarded further outbound." =
?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed to =
outbound.</div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>* Table 1 on page 50, the =
last row, capitalization:</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 =A0 </span>left column: "IPsec SPI", =
right column: "ipsec-SPI"</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div></div>That is intentionally, as =
the NATFW NSLP uses IPsec SPI as name and GIST uses =
ipsec-SPI.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Thanks a =
lot,=A0</div><div><br =
class=3D"webkit-block-placeholder"></div><div>=A0=A0Martin</div><div><br><=
div> <span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-size: =
12px; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
auto; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div><a =
href=3D"mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</a></d=
iv><div><br></div><div><div>NEC Laboratories Europe - Network Research =
Division</div><div><br class=3D"webkit-block-placeholder"></div><div>NEC =
Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014</div></div></span> =
</div><br></div></div></body></html>=

--Apple-Mail-17--457238117--



--===============1225577091==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1225577091==--





From nsis-bounces@ietf.org Thu Jan 24 10:45:58 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JI4H7-0001Ml-Vp; Thu, 24 Jan 2008 10:45:57 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JI4H5-0001MW-Hx
	for nsis-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 10:45:55 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JI4H5-0001MK-3X
	for nsis@ietf.org; Thu, 24 Jan 2008 10:45:55 -0500
Received: from smtp0.netlab.nec.de ([195.37.70.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JI4H3-00006Z-3Z
	for nsis@ietf.org; Thu, 24 Jan 2008 10:45:55 -0500
Received: from localhost (atlas1.office [127.0.0.1])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 9ED9028000627;
	Thu, 24 Jan 2008 16:45:52 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1])
	by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ToftutKrh282; Thu, 24 Jan 2008 16:45:52 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.netlab.nec.de (Postfix) with ESMTP id 74BFD28000455;
	Thu, 24 Jan 2008 16:45:42 +0100 (CET)
Received: from [10.1.1.109] ([10.1.1.109]) by mx1.office over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 24 Jan 2008 16:45:42 +0100
In-Reply-To: <Pine.LNX.4.64.0712191628400.7142@sbz-31.cs.Helsinki.FI>
References: <57BCC14C-53FD-4B9C-8EEE-C2D5D78B0B1F@netlab.nec.de>
	<Pine.LNX.4.64.0712191628400.7142@sbz-31.cs.Helsinki.FI>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <53BA84CF-4CD6-43AE-8976-B4870EF99C48@netlab.nec.de>
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Subject: Re: [NSIS] WGLC: draft-ietf-nsis-nslp-natfw-16.txt
Date: Thu, 24 Jan 2008 16:45:41 +0100
To: Teemu Huovila <thuovila@cs.helsinki.fi>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 24 Jan 2008 15:45:42.0389 (UTC)
	FILETIME=[2D107250:01C85EA0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: eee8f8a810071652260f5b6c3a710e46
Cc: nsis <nsis@ietf.org>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0748423759=="
Errors-To: nsis-bounces@ietf.org


--===============0748423759==
Content-Type: multipart/alternative; boundary=Apple-Mail-18--455957809


--Apple-Mail-18--455957809
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hi Teemu,


Am 19.12.2007 um 15:39 schrieb Teemu Huovila:

> Hello
>
> I have read the draft and I do not have any major objections. I  
> think it
> is very extensive and considers, in great detail,  all necessary  
> aspects
> of the protocol.
>
> I am very sorry, that my comments are overdue. I hope they can still
> be of some use for the working group. This was my first review of
> the draft and it took much longer to read, than I had estimated.

No problem, I also had trouble (w.r.t. time) to get to the NATFW NSLP.

>
> I have divided my comments into two categories. One group of  
> regular nits
> and another of more insignificant details. I include the comments  
> below.
>
> Before nits I will just add my 2 cents to the 5-tuple/policy rule
> discussion. As mentioned by Lauri, it is defined somewhat unclearly on
> page 20. It is, however, in my opinion defined more clearly on page  
> 10.
> It is also worth to note, that the first definition uses "and",  
> where the
> second uses '/'.

I hope it got better readable with Lauri's text.

>
> -----
> nits:
>
> * page 6, paragraph 2:
> "This message .... intercepts these messages," -> *this message*

Fixed.

>
> * page 7:
> "If the data receiver resides in a private addressing realm or
> firewall" --> *behind a* firewall ?

Yep, indeed. Fixed.

>
> * page 8:
> the second sentence in the definition of "Firewall" is superfluous.

Removed 2nd sentence.

>
> * page 9:
> In bullet about NATFW NSLP peer the term "NSIS adjacency" is vague.
> I suggest "NSLP adjacency" (or GIST/NTLP adjacency, if that was  
> intended). [2]
> defines GIST adjacency and "adjacent peer"

Fixed to NTLP adjacency.

>
> * page 25, 3.2.1, 3rd bullet:
> What are "inbound NATFW peers"? Does "inbound"
> here mean towards the NI?  (it became clear later, in section 3.7.5)

towards NI. But this inbound is wrong at that place,as NOTIFY can run  
in both directions. Removed 'inbound' at this occurrence.

>
> * page 30, 2nd paragraph:
> Error conditions are quite correctly defined for both
> too low and too high session lifetimes, but the text states:
>
> "The forwarders MUST accept the granted NATFW NSLP signaling  
> session lifetime,
> as long as this value is less than or equal to the acceptable value."
>
> later "lower or equal" is mentioned.
>
> Should these maybe be "if the lifetime value is within the  
> acceptable range",

Fixed to "if the lifetime value is within the acceptable range".

> or something similar? If not, I have great trouble understanding this.
>
> How are NFs on the path towards NR informed, if a node rejects the  
> lifetime
> suggested in the RESPONSE? A NOTIFY with the same error code?  Can  
> NOTIFY be
> sent towards NR? Page 66 says "The NOTIFY message is routed towards  
> the NI..."

I also have some doubts about this and started a separated thread  
about this (but with special focus to the error handling).

>
> Im very sorry, if I have overlooked some central detail about this.

No, you hit one remaining issues! :)

>
> * page 33, 5th bullet, sub-bullet:
> "If no matching reservation can be found, i.e. no reservation has  
> been made in
> advance, the NSLP MUST return an error RESPONSE of class 'Signaling  
> session
> failure' (0x6) with response code 'No reservation found matching  
> the MRI of the
> CREATE request' (0x03) MUST be generated."  --> "MUST be generated" is
> superfluous? (already "MUST return")

Fixed.

>
> * page 39-40:
> processing of EXT on NI(page 39) says: "When the data sender's IP  
> address is
> not known, the NI+ MUST NOT include a NATFW_DTINFO object."
>
> later, on page 40 it is stated:
> "The edge-NAT or any other NAT MUST reject EXT messages not carrying a
> NATFW_DTINFO object..."
>
> Was the "LE-MRM, DS unknown etc" case DTINFO object added by  
> somebody in the
> middle? A NAT before the edge-NAT? But arent those included in "or  
> any other
> NAT"?
>
> Also, NATFW_DTINFO is specified as mandatory, in 4.3.2 (page 64)  
> Maybe I have
> overlooked something here as well. The section, as Niklas  
> mentioned, is not
> very easy to read.

This part has been reworked, as there where multiple places  
contradicting each other.
Fixed.

>
> * page 46:
> "This proxy mode of operation must terminate the NATFW NSLP  
> signaling as
> topologically close to the terminal for which it is proxying and  
> proxy all
> messages."  --> *as possible* or something similar seems to be  
> missing from
> that sentence. (It only says "as close..." )

Replace it with "...signaling topologically-wise as close as possible  
to the terminal..."
This is typical editing error after x revisions. :)

>
> Also, what does this sentence mean? All proxy mode signaling is  
> terminated at
> the NI+/NI side edge-device, if I understood the section correctly.

Yes. However, there is some difficulty in saying where the proxies  
are located, as this depends on the system where this is implemented.  
Therefore this complicated sentence.

>
> ------------------------
> insignificant/uncertain:
>
> * page 7:
> "one or other" --> one or *the* other ?

Fixed.

>
> * page 9:
> The "SDA" did not become clear to me until page 36( with dr, dr+  
> etc). Though
> admittedly it is difficult to write a clear terminology section, if no
> knowledge can be expected from the reader, i.e. me. :)

But with page 36 it was clear? That's fair enough if it is clear at  
the point when it comes to importance.

>
> * page 11:
> "on the data path from... and the external network" "and" could be  
> *to*?
> (i.e. on the data path from ...to) or change "from" to *between*?

"and" is indeed "to". Fixed.

>
> * page 22, bullet 4:
> "Ni" -> *NI*

Fixed.

> * page 31, 3rd paragraph:
>   "NSLP MUST update its stored state accordingly, if permitted by  
> all security
>   checks (see Section 3.6), and stores"
>   --> *store*?

Fixed.

>
> * page 53:
> "The NSLP header is carried in all NATFW NSLP message and objects... "
> --> *messages*

Fixed. Again some editing bug...

>
> * page 63:
>   "Objects defined in this memo carry always the flag combination"
>   --> *always carry* ?

Fixed.

>
> * page 80:
>   "The rest of this section is giving"
>   --> *gives* ?

Fixed.

>
> * page 80:
>   "It necessary to differentiate" --> It *is*

Fixed.

Thanks!!!

   Martin


stiemerling@netlab.nec.de

NEC Laboratories Europe - Network Research Division

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


--Apple-Mail-18--455957809
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
Hi Teemu,=A0<div><br =
class=3D"webkit-block-placeholder"></div><div><br><div><div>Am =
19.12.2007 um 15:39 schrieb Teemu Huovila:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Hello</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">I have read the draft and I do =
not have any major objections. I think it</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">is very =
extensive and considers, in great detail,<span =
class=3D"Apple-converted-space">=A0 </span>all necessary =
aspects</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">of the protocol.</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I am =
very sorry, that my comments are overdue. I hope they can =
still</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">be of some use for the working =
group. This was my first review of</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">the draft and =
it took much longer to read, than I had =
estimated.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>No problem, I also had =
trouble (w.r.t. time) to get to the NATFW NSLP.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">I have divided my comments into two categories. One =
group of regular nits</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">and another of more =
insignificant details. I include the comments below.</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Before =
nits I will just add my 2 cents to the 5-tuple/policy rule</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">discussion. As mentioned by Lauri, it is defined =
somewhat unclearly on</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">page 20. It is, however, in =
my opinion defined more clearly on page 10.</div><div style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">It is =
also worth to note, that the first definition uses "and", where =
the</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">second uses =
'/'.</div></blockquote><div><br class=3D"webkit-block-placeholder"></div>I=
 hope it got better readable with Lauri's =
text.</div><div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">-----</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">nits:</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">* page =
6, paragraph 2:</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">"This message .... intercepts =
these messages," -&gt; *this message*</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">* page 7:<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">"If the =
data receiver resides in a private addressing realm or</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">firewall" --&gt; *behind a* firewall =
?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Yep, indeed. =
Fixed.</div><br><blockquote type=3D"cite"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">* page 8:<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">the =
second sentence in the definition of "Firewall" is =
superfluous.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Removed 2nd =
sentence.</div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">* page =
9:<span class=3D"Apple-converted-space">=A0</span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">In bullet about NATFW NSLP peer the term "NSIS =
adjacency" is vague.</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">I suggest "NSLP adjacency" =
(or GIST/NTLP adjacency, if that was intended). [2]</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">defines GIST adjacency and "adjacent =
peer"</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed to NTLP =
adjacency.=A0</div><br><blockquote type=3D"cite"><div style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">* page 25, =
3.2.1, 3rd bullet:<span class=3D"Apple-converted-space">=A0</span></div><d=
iv style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">What are "inbound NATFW peers"? Does =
"inbound"</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">here mean towards the NI?<span =
class=3D"Apple-converted-space">=A0 </span>(it became clear later, in =
section 3.7.5)</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>towards NI. But this =
inbound is wrong at that place,as NOTIFY can run in both directions. =
Removed 'inbound' at this occurrence.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">* page 30, 2nd paragraph:<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Error =
conditions are quite correctly defined for both</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">too low and too high session lifetimes, but the text =
states:</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">"The forwarders MUST accept the granted NATFW NSLP =
signaling session lifetime,</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">as long as =
this value is less than or equal to the acceptable value."</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">later =
"lower or equal" is mentioned.</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Should these maybe be "if the =
lifetime value is within the acceptable =
range",</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed to "if the lifetime =
value is within the acceptable range".</div><div><br =
class=3D"webkit-block-placeholder"></div><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">or something similar? If not, I have great trouble =
understanding this.</div></blockquote><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">How are =
NFs on the path towards NR informed, if a node rejects the =
lifetime</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">suggested in the RESPONSE? A =
NOTIFY with the same error code?<span class=3D"Apple-converted-space">=A0 =
</span>Can NOTIFY be</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">sent towards NR? Page 66 =
says "The NOTIFY message is routed towards the =
NI..."</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div>I also have some doubts about =
this and started a separated thread about this (but with special focus =
to the error handling).</div><div><br><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Im very =
sorry, if I have overlooked some central detail about =
this.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>No, you hit one remaining =
issues! :)</div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">* page 33, =
5th bullet, sub-bullet:<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">"If no =
matching reservation can be found, i.e. no reservation has been made =
in</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; ">advance, the NSLP MUST return an error RESPONSE =
of class 'Signaling session</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">failure' =
(0x6) with response code 'No reservation found matching the MRI of =
the</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">CREATE request' (0x03) MUST be =
generated."<span class=3D"Apple-converted-space">=A0 </span>--&gt; "MUST =
be generated" is</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">superfluous? (already "MUST =
return")</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">* page 39-40:<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">processing of EXT on NI(page 39) says: "When the data sender's IP =
address is</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">not known, the NI+ MUST NOT =
include a NATFW_DTINFO object."</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">later, on page 40 it is =
stated:</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">"The edge-NAT or any other NAT =
MUST reject EXT messages not carrying a</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">NATFW_DTINFO object..."</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Was the "LE-MRM, DS unknown etc" =
case DTINFO object added by somebody in the</div><div style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">middle? =
A NAT before the edge-NAT? But arent those included in "or any =
other</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">NAT"?</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Also, =
NATFW_DTINFO is specified as mandatory, in 4.3.2 (page 64) Maybe I =
have</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">overlooked something here as =
well. The section, as Niklas mentioned, is not</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">very easy to read.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>This part has been =
reworked, as there where multiple places contradicting each =
other.</div><div>Fixed.</div><br><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">* page =
46:<span class=3D"Apple-converted-space">=A0</span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">"This proxy mode of operation must terminate the =
NATFW NSLP signaling as</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">topologically =
close to the terminal for which it is proxying and proxy all</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">messages."<span class=3D"Apple-converted-space">=A0 =
</span>--&gt; *as possible* or something similar seems to be missing =
from</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">that sentence. (It only says "as =
close..." )</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Replace it with =
"...signaling topologically-wise as close as possible to the =
terminal..."</div><div>This is typical editing error after x revisions. =
:)</div><div><br class=3D"webkit-block-placeholder"></div><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Also, what does this sentence mean? All proxy mode =
signaling is terminated at</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">the NI+/NI =
side edge-device, if I understood the section =
correctly.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Yes. However, there is =
some difficulty in saying where the proxies are located, as this depends =
on the system where this is implemented. Therefore this complicated =
sentence.</div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">------------------------</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">insignificant/uncertain:</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">* page 7:</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">"one or other" --&gt; one or *the* other =
?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">* page 9:<span =
class=3D"Apple-converted-space">=A0</span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The =
"SDA" did not become clear to me until page 36( with dr, dr+ etc). =
Though</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">admittedly it is difficult to =
write a clear terminology section, if no</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">knowledge can be expected from the reader, i.e. me. =
:)</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>But with page 36 it was =
clear? That's fair enough if it is clear at the point when it comes to =
importance.</div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">* page =
11:<span class=3D"Apple-converted-space">=A0</span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">"on the data path from... and the external network" =
"and" could be *to*?</div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">(i.e. on the data path from =
...to) or change "from" to *between*?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>"and" is indeed "to". =
Fixed.</div><br><blockquote type=3D"cite"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">* page 22, bullet 4:</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">"Ni" -&gt; *NI*</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">* page 31, 3rd =
paragraph:</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>"NSLP MUST update its stored =
state accordingly, if permitted by all security</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0 =
</span>checks (see Section 3.6), and stores"</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0 =
</span>--&gt; *store*?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">* page 53:</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">"The NSLP =
header is carried in all NATFW NSLP message and objects... "</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">--&gt; *messages*</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed. Again some editing =
bug...</div><br><blockquote type=3D"cite"><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><br></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">* page 63:</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0 =
</span>"Objects defined in this memo carry always the flag =
combination"</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>--&gt; *always carry* =
?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.=A0</div><br><blockquo=
te type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">* page 80:</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>"The rest of this section is =
giving"</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>--&gt; *gives* =
?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">* page 80:</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0 </span>"It necessary to =
differentiate" --&gt; It *is*</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Fixed.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Thanks!!!</div><div><br =
class=3D"webkit-block-placeholder"></div><div>=A0=A0Martin</div><div><br =
class=3D"webkit-block-placeholder"></div><div><br =
class=3D"webkit-block-placeholder"></div><div><a =
href=3D"mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</a></d=
iv></div><div><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-size: =
12px; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
auto; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div><br></div><div><div>NEC =
Laboratories Europe - Network Research Division</div><div><br =
class=3D"webkit-block-placeholder"></div><div>NEC Europe Limited | =
Registered Office: NEC House, 1 Victoria Road, London W3 6BL | =
Registered in England 2832014</div></div></span> =
</div><br></div></body></html>=

--Apple-Mail-18--455957809--



--===============0748423759==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0748423759==--





From nsis-bounces@ietf.org Mon Jan 28 08:18:34 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJTsd-0003li-Hl; Mon, 28 Jan 2008 08:18:31 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JJTsb-0003la-Tp
	for nsis-confirm+ok@megatron.ietf.org; Mon, 28 Jan 2008 08:18:29 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJTsb-0003lS-Gk
	for nsis@ietf.org; Mon, 28 Jan 2008 08:18:29 -0500
Received: from smtp0.neclab.eu ([195.37.70.41])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJTsa-0003XZ-6K
	for nsis@ietf.org; Mon, 28 Jan 2008 08:18:29 -0500
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 7C11B2C01D460;
	Mon, 28 Jan 2008 14:18:27 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1])
	by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zlyOG+x-UEZ6; Mon, 28 Jan 2008 14:18:27 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 543CB2C01D45F;
	Mon, 28 Jan 2008 14:18:17 +0100 (CET)
Received: from [10.1.1.109] ([10.1.1.109]) by mx1.office over TLS secured
	channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 28 Jan 2008 14:18:17 +0100
In-Reply-To: <476BE274.9030307@uni-tuebingen.de>
References: <57BCC14C-53FD-4B9C-8EEE-C2D5D78B0B1F@netlab.nec.de>	<Pine.LNX.4.64.0712042046330.9630@sbz-31.cs.Helsinki.FI>
	<E4357D7C-FA92-4185-B833-247E76EAF3D9@netlab.nec.de>
	<476BE274.9030307@uni-tuebingen.de>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <BEF2F2BF-330A-4554-B644-942424BA1135@netlab.nec.de>
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Subject: Re: [NSIS] WGLC: draft-ietf-nsis-nslp-natfw-16.txt
Date: Mon, 28 Jan 2008 14:18:16 +0100
To: Ali Fessi <ali.fessi@uni-tuebingen.de>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 28 Jan 2008 13:18:17.0699 (UTC)
	FILETIME=[3EDEDB30:01C861B0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6907f330301e69261fa73bed91449a20
Cc: nsis <nsis@ietf.org>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1431840566=="
Errors-To: nsis-bounces@ietf.org


--===============1431840566==
Content-Type: multipart/alternative; boundary=Apple-Mail-2--119202473


--Apple-Mail-2--119202473
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed


Am 21.12.2007 um 16:57 schrieb Ali Fessi:

> Dear Martin and NATFW NSLP co-authors,
>
>
> I have read the draft and have only few comments:
>
> - First, I think the draft needs some editorial polishing and needs  
> to become a bit more reader-friendly where possible. As already  
> mentioned in some emails before, some sections are difficult to  
> understand even with background knowledge in NATFW NSLP. Some more  
> cross references to different sections within the draft itself or  
> to sections in other drafts considered as background knowledge,  
> e.g. GIST, could be helpful to make life easier for the reader.

Good to know that there are some parts which are hard to read.  
However, this is a WG document and all people are invited to propose  
new text for replacing existing text.
It is quite hard for me as a document editor to judge which parts are  
hard to read and which are not. Furthermore, text is usually written  
in the writer's style and only real replacement text can improve  
readability.

>
> - The solution described for the scenario "2.6 Both End Hosts  
> Behind Same NAT" is not efficient. I guess you know what I am  
> talking about here. All the traffic will go through the external  
> gateway. I remember we had some discussions with Cedric about 4  
> years ago about using something like ICE (at that time ICE was  
> pretty new, I think) in order to discover whether the peer is  
> within the same network in order to perform direct signaling and  
> route the traffic directly between the peers.

There has been an AD decision (back in Alison's days) to not go into  
ICE specifics.
Technically you are completely write, but protocol wise I would  
assume that interworking with ICE would require a new document, e.g.  
applicability statement.

>
> - The text in "C.4.  NSLP Handling of Twice-NAT" is a bit  
> confusing. e.g. "The dynamic configuration of twice-NATs requires  
> application level
>    support, as stated in Section 2.5.  The NATFW NSLP cannot be  
> used for
>    configuring twice-NATs if application level support is needed."
>
> does this mean that the NATFW NSLP does not supports twice-NATs and  
> it is left to application layer support?

Twice-NAT configuration is not supported, as twice-NAT is marked as  
historic (RFC 4966).

>
> or "The NSLP is probably able to traverse the twice-NAT" (I guess  
> with "probably" here, you mean it depends on whether the twice-NAT  
> is NATFW NSLP aware or not. This could be clarified better).

It is meant as, whenever people do consider twice-NATs and they are  
implementing the NATFW NSLP, they should at least take care that IP  
addresses are exchanged in a proper way. However, there is no text  
here which defines the standard way of doing so. The reason for this  
is the current status of twice-NAT (NAT-PT) in the IETF (RFC 4966).


>
> - The text about CMS in the security section is a bit confusing:
>
> "Additionally, security protection of certain
>    payloads may be required between non-neighboring signaling entities
>    and the Cryptographic Message Syntax (CMS) [14] might be a  
> potential
>    solution.  Payload protection using CMS is not described in this
>    document."
>
> This sounds like: "you could use CMS, but we are not sure if it  
> will solve your problems, or we don't know even how to use it here,  
> and which message parts you will need to protect".
>
> I am not sure here, but I think that if you use CMS, you will use  
> it to protect the authorizations tokens, so the use of CMS could be  
> moved the NSLP authorization draft. What do you think?

I'm fine with removing it, as it really reads shaky...

>
> Otherwise, I hope that the effort of several years will be fruiful  
> and that we will have a successful protocol! :-)

Thanks! :)

stiemerling@netlab.nec.de

NEC Laboratories Europe - Network Research Division

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


--Apple-Mail-2--119202473
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<br><div><div>Am 21.12.2007 um 16:57 schrieb Ali Fessi:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Dear Martin and NATFW NSLP co-authors,</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I have read =
the draft and have only few comments:</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">- First, I =
think the draft needs some editorial polishing and needs to become a bit =
more reader-friendly where possible. As already mentioned in some emails =
before, some sections are difficult to understand even with background =
knowledge in NATFW NSLP. Some more cross references to different =
sections within the draft itself or to sections in other drafts =
considered as background knowledge, e.g. GIST, could be helpful to make =
life easier for the reader.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Good to know that there =
are some parts which are hard to read. However, this is a WG document =
and all people are invited to propose new text for replacing existing =
text.=A0</div><div>It is quite hard for me as a document editor to judge =
which parts are hard to read and which are not. Furthermore, text is =
usually written in the writer's style and only real replacement text can =
improve readability.=A0</div><br><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">- The =
solution described for the scenario "2.6 Both End Hosts Behind Same NAT" =
is not efficient. I guess you know what I am talking about here. All the =
traffic will go through the external gateway. I remember we had some =
discussions with Cedric about 4 years ago about using something like ICE =
(at that time ICE was pretty new, I think) in order to discover whether =
the peer is within the same network in order to perform direct signaling =
and route the traffic directly between the =
peers.</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>There has been an AD =
decision (back in Alison's days) to not go into ICE =
specifics.=A0</div><div>Technically you are completely write, but =
protocol wise I would assume that interworking with ICE would require a =
new document, e.g. applicability statement.=A0</div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- The text in "C.4.<span =
class=3D"Apple-converted-space">=A0 </span>NSLP Handling of Twice-NAT" =
is a bit confusing. e.g. "The dynamic configuration of twice-NATs =
requires application level</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>support, as stated in =
Section 2.5.<span class=3D"Apple-converted-space">=A0 </span>The NATFW =
NSLP cannot be used for</div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>configuring twice-NATs if =
application level support is needed."</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">does this =
mean that the NATFW NSLP does not supports twice-NATs and it is left to =
application layer support?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Twice-NAT configuration is =
not supported, as twice-NAT is marked as historic =
(RFC=A04966).</div><br><blockquote type=3D"cite"><div style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">or "The NSLP =
is probably able to traverse the twice-NAT" (I guess with "probably" =
here, you mean it depends on whether the twice-NAT is NATFW NSLP aware =
or not. This could be clarified better).</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>It is meant as, whenever =
people do consider twice-NATs and they are implementing the NATFW NSLP, =
they should at least take care that IP addresses are exchanged in a =
proper way. However, there is no text here which defines the standard =
way of doing so. The reason for this is the current status of twice-NAT =
(NAT-PT) in the IETF (RFC=A04966).</div><div><br></div><br><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">- The text about CMS in the security section is a =
bit confusing:</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">"Additionally, security protection of =
certain</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>payloads may be required =
between non-neighboring signaling entities</div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span =
class=3D"Apple-converted-space">=A0=A0 </span>and the Cryptographic =
Message Syntax (CMS) [14] might be a potential</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0=A0 =
</span>solution.<span class=3D"Apple-converted-space">=A0 </span>Payload =
protection using CMS is not described in this</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><span class=3D"Apple-converted-space">=A0=A0 =
</span>document."</div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">This sounds like: "you could use CMS, but we are not =
sure if it will solve your problems, or we don't know even how to use it =
here, and which message parts you will need to protect".</div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I am not =
sure here, but I think that if you use CMS, you will use it to protect =
the authorizations tokens, so the use of CMS could be moved the NSLP =
authorization draft. What do you think?</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>I'm fine with removing it, =
as it really reads shaky...</div><br><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Otherwise, I hope that the effort of several years will be fruiful and =
that we will have a successful protocol! :-)</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Thanks! =
:)</div><div><br></div></div><div> <span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Lucida Grande'; font-size: 12px; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; "><div><a =
href=3D"mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</a></d=
iv><div><br></div><div><div>NEC Laboratories Europe - Network Research =
Division</div><div><br class=3D"webkit-block-placeholder"></div><div>NEC =
Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014</div></div></span> =
</div><br></body></html>=

--Apple-Mail-2--119202473--



--===============1431840566==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1431840566==--





From nsis-bounces@ietf.org Mon Jan 28 09:30:30 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJV0I-0007cI-1T; Mon, 28 Jan 2008 09:30:30 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JJV0G-0007RG-5D
	for nsis-confirm+ok@megatron.ietf.org; Mon, 28 Jan 2008 09:30:28 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JJV0F-0007R8-Rx
	for nsis@ietf.org; Mon, 28 Jan 2008 09:30:27 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJUyu-0005Cf-5Z
	for nsis@ietf.org; Mon, 28 Jan 2008 09:29:04 -0500
Received: from smtp0.neclab.eu ([195.37.70.41])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJUys-0005G1-O4
	for nsis@ietf.org; Mon, 28 Jan 2008 09:29:04 -0500
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 4CEC42C01D51B;
	Mon, 28 Jan 2008 15:29:02 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1])
	by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sya0iKtXM2Dp; Mon, 28 Jan 2008 15:29:02 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 260D72C01D51A;
	Mon, 28 Jan 2008 15:28:52 +0100 (CET)
Received: from 10.1.1.109 ([10.1.1.109]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Mon, 28 Jan 2008 14:28:52 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Mon, 28 Jan 2008 15:28:51 +0100
Subject: Re: [NSIS] WGLC: draft-ietf-nsis-nslp-natfw-16.txt
From: Martin Stiemerling <Stiemerling@nw.neclab.eu>
To: Lauri J T Liuhto <lliuhto@cs.helsinki.fi>
Message-ID: <C3C3A533.E898%Stiemerling@nw.neclab.eu>
Thread-Topic: [NSIS] WGLC: draft-ietf-nsis-nslp-natfw-16.txt
Thread-Index: AchhuhodWGVMYM2tEdyTkgAWy5Ti1Q==
In-Reply-To: <65BB5B95-FBB4-4124-AA97-3562002CCAAA@netlab.nec.de>
Mime-version: 1.0
X-Spam-Score: 1.8 (+)
X-Scan-Signature: fec852dbea6d068499ed3250edf328e2
X-TMDA-Confirmed: Mon, 28 Jan 2008 09:30:27 -0500
Cc: nsis <nsis@ietf.org>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1567098595=="
Errors-To: nsis-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1567098595==
Content-type: multipart/alternative;
	boundary="B_3284378931_303552"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3284378931_303552
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Just as an addendum:

IPsec SPI has been changed to IPsec-SPI.

  Martin

Am 24.01.2008 16:24 Uhr schrieb "Martin Stiemerling" unter
<stiemerling@netlab.nec.de>:

> Hi=A0Lauri,
>=20
> Am 13.12.2007 um 01:08 schrieb Lauri J T Liuhto:
>=20
>> On Fri, 23 Nov 2007, Martin Stiemerling wrote:
>> =20
>>> The authors believe that the NATFW NSLP
>>> (draft-ietf-nsis-nslp-natfw-16.txt) is ready for WGLC.
>>> The WGLC starts today and will run until December 14th.
>>> =20
>>=20
>> =A0Hi,=A0
>>=20
>> =A0I have read the document, and I did not find any big issues, mainly=A0
>> just some editorial things. I did not repeat findings already=A0
>> provided by Jukka or Niklas.
>>=20
>> =A0Some parts of the text, mainly Section 3 (Protocol Description), was=A0
>> such, that I can not be sure whether I understood it completely. The=A0
>> text itself was quite easy to read, but I think those who have=A0
>> implemented this protocol can say more accurately how well the protocol=A0
>> actually is described.=A0
>>=20
>> =A0To make it short: I think the specification is in quite nice state, and=
=A0
>> needs just some editorial fixes.
>=20
> Thanks! :)
>=20
>>=20
>> Here are my comments on the draft:
>>=20
>> =A0* At page 11, line 571: 'routeable' --> 'routable' (?)
>=20
> Fixed.
>=20
>>=20
>> =A0* Examples in Section 2 use mainly 'MB' in figures to represent NAT
>> =A0=A0 and/or FW nodes. However, I think the use is not always
>> =A0=A0 consistent. For example, in the figure 2 'FW' is used (and I think
>> =A0=A0 it is ok, because the text explicitly states that this example is
>> =A0=A0 about FW-only cases), but figure 9 in section 2.8 has 'MB's
>> =A0=A0 instead. If those middle boxes in scenario 2.8 may be also NATs, I
>> =A0=A0 think it would be nice to have it in text. If those middle boxes
>> =A0=A0 are always firewalls as I think the text states, then the figure
>> =A0=A0 should be changed.
>>=20
>> =A0=A0 However, I think that the text is clear enough already, and the
>> =A0=A0 easy fix would be to change the 'FW' boxes to 'MB' boxes in the=A0
>> =A0=A0 figure 2 :)
>=20
> 2.8 and 2.7 have a subtle difference and it is better to change MB to FW =
in
> figure 9.
>=20
>>=20
>> =A0* Section 3.1 Policy Rules, first paragraph:
>>=20
>> =A0"For firewalls the policy rule usually consists of a 5-tuple, source/
>> =A0 destination addresses, transport protocol, and source/destination
>> =A0 port numbers, plus an action, such as allow or deny."
>>=20
>> =A0 At least before reading the rest of the document, the word 'usually'
>> =A0 seems a bit odd here. Do real alternative policy rules that do not
>> =A0 contain the 5-tuple and action exist?
>>=20
>> =A0 I also think this sentence is not too clear, some kind of
>> =A0 reformatting would be nice. For example, something like this (still
>> =A0 having the word 'usually'):
>>=20
>> =A0"For firewalls the policy rule usually consists of a 5-tuple and an
>> =A0 action such as allow or deny. The information contained in the tuple
>> =A0 includes source/destination addresses, transport protocol and
>> =A0 source/destination port numbers."
>=20
> This reads better! Replaced it.
>=20
>>=20
>> =A0* In addition to comments Niklas already gave on figure 11 on page
>> =A0=A0 24, I want to add that the figure and its legend do not
>> =A0=A0 match. There is no MB2 in the figure, and NF is present in the
>> =A0=A0 legend only in the text. As Niklas, I also think that it would be
>> =A0=A0 good to point out which node belongs to which network.
>=20
> Fixed.
>=20
>>=20
>> =A0* Page 28, last bullet:
>> =A0 "the lease time of the NI's IP address.=A0 The chosen NATFW NSLP
>> =A0=A0 signaling session lifetime must be larger than the lease time,
>> =A0=A0 otherwise the IP address can be re-assigned to a different node.
>> =A0=A0 This node may receive unwanted traffic, although it never has
>> =A0=A0 requested a NAT/firewall configuration, which might be an issue in
>> =A0=A0 mobile environments.
>>=20
>> =A0=A0 I just can not get the idea :) Should it be 'must be smaller than
>> =A0=A0 the lease time' ? If not, then I think some more text is needed.
>=20
> Yep, you're right, it must be smaller. I also bumped in this when reading=
.
> Fixed.
>=20
>>=20
>> =A0* Page 45, middle bullet:
>> =A0=A0 "and outbound messages MUST be forwarded further inbound."=A0
>> =A0=A0 ->
>> =A0=A0 "and outbound messages MUST be forwarded further outbound." ?
>=20
> Fixed to outbound.
>=20
>>=20
>> =A0 * Table 1 on page 50, the last row, capitalization:
>> =A0 =A0 left column: "IPsec SPI", right column: "ipsec-SPI"
>=20
> That is intentionally, as the NATFW NSLP uses IPsec SPI as name and GIST =
uses
> ipsec-SPI.
>=20
> Thanks a lot,=A0
>=20
> =A0=A0Martin
>=20
> =20
> stiemerling@netlab.nec.de
>=20
> NEC Laboratories Europe - Network Research Division
>=20
> NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, Londo=
n W3
> 6BL | Registered in England 2832014
> =20
>=20
>=20
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis



--B_3284378931_303552
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [NSIS] WGLC: draft-ietf-nsis-nslp-natfw-16.txt</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'>Just =
as an addendum: <BR>
<BR>
IPsec SPI has been changed to IPsec-SPI.<BR>
<BR>
&nbsp;&nbsp;Martin<BR>
<BR>
Am 24.01.2008 16:24 Uhr schrieb &quot;Martin Stiemerling&quot; unter &lt;st=
iemerling@netlab.nec.de&gt;:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'>Hi=A0Lauri,<BR>
<BR>
Am 13.12.2007 um 01:08 schrieb Lauri J T Liuhto:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'>On Fri, 23 Nov 2007, Martin Stiemerling wrote:<BR>
&nbsp;<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'>The authors believe that the NATFW NSLP<BR>
(draft-ietf-nsis-nslp-natfw-16.txt) is ready for WGLC.<BR>
The WGLC starts today and will run until December 14th.<BR>
&nbsp;<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'><BR>
=A0Hi,=A0<BR>
<BR>
=A0I have read the document, and I did not find any big issues, mainly=A0<BR>
just some editorial things. I did not repeat findings already=A0<BR>
provided by Jukka or Niklas.<BR>
<BR>
=A0Some parts of the text, mainly Section 3 (Protocol Description), was=A0<BR>
such, that I can not be sure whether I understood it completely. The=A0<BR>
text itself was quite easy to read, but I think those who have=A0<BR>
implemented this protocol can say more accurately how well the protocol=A0<BR=
>
actually is described.=A0<BR>
<BR>
=A0To make it short: I think the specification is in quite nice state, and=A0<B=
R>
needs just some editorial fixes.<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'><BR>
Thanks! :)<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'><BR>
Here are my comments on the draft:<BR>
<BR>
=A0* At page 11, line 571: 'routeable' --&gt; 'routable' (?)<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'><BR>
Fixed.<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'><BR>
=A0* Examples in Section 2 use mainly 'MB' in figures to represent NAT<BR>
=A0=A0 and/or FW nodes. However, I think the use is not always<BR>
=A0=A0 consistent. For example, in the figure 2 'FW' is used (and I think<BR>
=A0=A0 it is ok, because the text explicitly states that this example is<BR>
=A0=A0 about FW-only cases), but figure 9 in section 2.8 has 'MB's<BR>
=A0=A0 instead. If those middle boxes in scenario 2.8 may be also NATs, I<BR>
=A0=A0 think it would be nice to have it in text. If those middle boxes<BR>
=A0=A0 are always firewalls as I think the text states, then the figure<BR>
=A0=A0 should be changed.<BR>
<BR>
=A0=A0 However, I think that the text is clear enough already, and the<BR>
=A0=A0 easy fix would be to change the 'FW' boxes to 'MB' boxes in the=A0<BR>
=A0=A0 figure 2 :)<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'><BR>
2.8 and 2.7 have a subtle difference and it is better to change MB to FW in=
 figure 9.<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'><BR>
=A0* Section 3.1 Policy Rules, first paragraph:<BR>
<BR>
=A0&quot;For firewalls the policy rule usually consists of a 5-tuple, source/=
<BR>
=A0 destination addresses, transport protocol, and source/destination<BR>
=A0 port numbers, plus an action, such as allow or deny.&quot;<BR>
<BR>
=A0 At least before reading the rest of the document, the word 'usually'<BR>
=A0 seems a bit odd here. Do real alternative policy rules that do not<BR>
=A0 contain the 5-tuple and action exist?<BR>
<BR>
=A0 I also think this sentence is not too clear, some kind of<BR>
=A0 reformatting would be nice. For example, something like this (still<BR>
=A0 having the word 'usually'):<BR>
<BR>
=A0&quot;For firewalls the policy rule usually consists of a 5-tuple and an<B=
R>
=A0 action such as allow or deny. The information contained in the tuple<BR>
=A0 includes source/destination addresses, transport protocol and<BR>
=A0 source/destination port numbers.&quot;<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'><BR>
This reads better! Replaced it.<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'><BR>
=A0* In addition to comments Niklas already gave on figure 11 on page<BR>
=A0=A0 24, I want to add that the figure and its legend do not<BR>
=A0=A0 match. There is no MB2 in the figure, and NF is present in the<BR>
=A0=A0 legend only in the text. As Niklas, I also think that it would be<BR>
=A0=A0 good to point out which node belongs to which network.<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'><BR>
Fixed.<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'><BR>
=A0* Page 28, last bullet:<BR>
=A0 &quot;the lease time of the NI's IP address.=A0 The chosen NATFW NSLP<BR>
=A0=A0 signaling session lifetime must be larger than the lease time,<BR>
=A0=A0 otherwise the IP address can be re-assigned to a different node.<BR>
=A0=A0 This node may receive unwanted traffic, although it never has<BR>
=A0=A0 requested a NAT/firewall configuration, which might be an issue in<BR>
=A0=A0 mobile environments.<BR>
<BR>
=A0=A0 I just can not get the idea :) Should it be 'must be smaller than<BR>
=A0=A0 the lease time' ? If not, then I think some more text is needed.<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'><BR>
Yep, you're right, it must be smaller. I also bumped in this when reading. =
Fixed.<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'><BR>
=A0* Page 45, middle bullet:<BR>
=A0=A0 &quot;and outbound messages MUST be forwarded further inbound.&quot;=A0<BR=
>
=A0=A0 -&gt;<BR>
=A0=A0 &quot;and outbound messages MUST be forwarded further outbound.&quot; ?<=
BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'><BR>
Fixed to outbound.<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'><BR>
=A0 * Table 1 on page 50, the last row, capitalization:<BR>
=A0 =A0 left column: &quot;IPsec SPI&quot;, right column: &quot;ipsec-SPI&quot;=
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'><BR>
That is intentionally, as the NATFW NSLP uses IPsec SPI as name and GIST us=
es ipsec-SPI.<BR>
<BR>
Thanks a lot,=A0<BR>
<BR>
=A0=A0Martin<BR>
<BR>
&nbsp;<BR>
stiemerling@netlab.nec.de<BR>
<BR>
NEC Laboratories Europe - Network Research Division<BR>
<BR>
NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014<BR>
&nbsp;<BR>
<BR>
<BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"></SPAN></FONT><FONT SIZE=3D"2"><FONT FA=
CE=3D"Monaco, Courier New"><SPAN STYLE=3D'font-size:10.0px'>____________________=
___________________________<BR>
nsis mailing list<BR>
nsis@ietf.org<BR>
https://www1.ietf.org/mailman/listinfo/nsis<BR>
</SPAN></FONT></FONT></BLOCKQUOTE><FONT SIZE=3D"2"><FONT FACE=3D"Monaco, Courie=
r New"><SPAN STYLE=3D'font-size:10.0px'><BR>
</SPAN></FONT></FONT>
</BODY>
</HTML>


--B_3284378931_303552--





--===============1567098595==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1567098595==--







From nsis-bounces@ietf.org Wed Jan 30 03:37:47 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JK8S2-0001hp-4a; Wed, 30 Jan 2008 03:37:46 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JK8S0-0001fb-TS
	for nsis-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 03:37:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JK8Rv-0001ZX-7e
	for nsis@ietf.org; Wed, 30 Jan 2008 03:37:39 -0500
Received: from smtp0.neclab.eu ([195.37.70.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JK8Rt-0002Vr-4s
	for nsis@ietf.org; Wed, 30 Jan 2008 03:37:39 -0500
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 9C4802C01D461
	for <nsis@ietf.org>; Wed, 30 Jan 2008 09:37:36 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1])
	by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9Mqu+rHSFaih for <nsis@ietf.org>;
	Wed, 30 Jan 2008 09:37:36 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 7D6E42C01D45F
	for <nsis@ietf.org>; Wed, 30 Jan 2008 09:37:31 +0100 (CET)
Received: from 10.1.1.109 ([10.1.1.109]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Wed, 30 Jan 2008 08:37:31 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Wed, 30 Jan 2008 09:37:29 +0100
Subject: Re: [NSIS] NATFW issue: state 'transit' timer definition
From: Martin Stiemerling <Stiemerling@nw.neclab.eu>
To: nsis <nsis@ietf.org>
Message-ID: <C3C5F5D9.EA12%Stiemerling@nw.neclab.eu>
Thread-Topic: [NSIS] NATFW issue: state 'transit' timer definition
Thread-Index: AchjG1kWl7hu2s8OEdyTkgAWy5Ti1Q==
In-Reply-To: <5B37E709-9B27-4490-B2EF-FAB14235153E@netlab.nec.de>
Mime-version: 1.0
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 86f85b2f88b0d50615aed44a7f9e33c7
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0514157001=="
Errors-To: nsis-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0514157001==
Content-type: multipart/alternative;
	boundary="B_3284530649_2855303"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3284530649_2855303
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

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

Hi,

I do assume that everybody is fine with the proposed change.

If not, please speak up now!

Thanks,=20

  Martin (as NATFW NSLP author)


Am 24.01.2008 11:22 Uhr schrieb "Martin Stiemerling" unter
<stiemerling@netlab.nec.de>:

> [writing with chair's hat off, i.e., as NATFW NSLP author only!]
>=20
> Hi all,
>=20
> I finally found time to get back to the NATFW NSLP and your WGLC comments=
.
> Thanks to all who did a review and sent in their comments!
>=20
> I also have done a complete review of=A0draft-ietf-nsis-nslp-natfw-16.txt a=
nd
> found some issues to be discussed. There will be separate e-mails for eac=
h
> issue I've found.=A0
>=20
> Here we go:
>=20
> In Section=A03.2.8.=A0 NATFW NSLP Signaling Sessions the different conceptual
> states of the a NATFW NSLP signaling session are defined. I see all state=
s are
> fine except the last one which is 'transit':
>=20
> Transit: The node has received an asynchronous message, i.e., a
> NOTIFY, and can delete the NATFW NSLP signaling session if needed.
> When a node has received a NOTIFY message (for instance,
> indicating a route change) it marks it as 'Transit' and deletes
> this NATFW NSLP signaling session if it is unused for some time
> specific to the local node. =A0This idle time does not need to be
> fixed, since it can depend on the node local maintenance cycle,
> i.e., the NATFW NSLP signaling session could be deleted if the
> node runs it garbage collection cycle.
>=20
> The issue is see, is the undefined timer value in this state. It simply s=
ays
> "...for some time..." which can result in implementations removing state
> immediately (time =3D 0), wait for seconds or minutes, or do never remove t=
he
> state (would be a bug indeed).=A0
>=20
> I personally would prefer to either give a fixed value or to give a formu=
la to
> calculate this time in a=A0standardised=A0way.=A0
>=20
> My proposal: Set this timer to 30 seconds fixed, as if there is no updati=
ng
> CREATE or EXTERNAL message within 30 seconds to a 'transit' state there w=
on't
> be anything beyond this anymore.
>=20
> =A0=A0Martin
>=20
> =20
> stiemerling@netlab.nec.de
>=20
> NEC Laboratories Europe - Network Research Division
>=20
> NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, Londo=
n W3
> 6BL | Registered in England 2832014
> =20
>=20
>=20
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis



--B_3284530649_2855303
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [NSIS] NATFW issue: state 'transit' timer definition</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'>[writ=
ing with chair's hat off, i.e., as NATFW NSLP author only!]<BR>
<BR>
Hi,<BR>
<BR>
I do assume that everybody is fine with the proposed change. <BR>
<BR>
If not, please speak up now!<BR>
<BR>
Thanks, <BR>
<BR>
&nbsp;&nbsp;Martin (as NATFW NSLP author)<BR>
<BR>
<BR>
Am 24.01.2008 11:22 Uhr schrieb &quot;Martin Stiemerling&quot; unter &lt;st=
iemerling@netlab.nec.de&gt;:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'>[writing with chair's hat off, i.e., as NATFW NSLP auth=
or only!]<BR>
<BR>
Hi all,<BR>
<BR>
I finally found time to get back to the NATFW NSLP and your WGLC comments. =
Thanks to all who did a review and sent in their comments!<BR>
<BR>
I also have done a complete review of=A0draft-ietf-nsis-nslp-natfw-16.txt and=
 found some issues to be discussed. There will be separate e-mails for each =
issue I've found.=A0<BR>
<BR>
Here we go:<BR>
<BR>
In Section=A03.2.8.=A0 NATFW NSLP Signaling Sessions the different conceptual s=
tates of the a NATFW NSLP signaling session are defined. I see all states ar=
e fine except the last one which is 'transit':<BR>
<BR>
Transit: The node has received an asynchronous message, i.e., a<BR>
NOTIFY, and can delete the NATFW NSLP signaling session if needed.<BR>
When a node has received a NOTIFY message (for instance,<BR>
indicating a route change) it marks it as 'Transit' and deletes<BR>
this NATFW NSLP signaling session if it is unused for some time<BR>
specific to the local node. =A0This idle time does not need to be<BR>
fixed, since it can depend on the node local maintenance cycle,<BR>
i.e., the NATFW NSLP signaling session could be deleted if the<BR>
node runs it garbage collection cycle.<BR>
<BR>
The issue is see, is the undefined timer value in this state. It simply say=
s &quot;...for some time...&quot; which can result in implementations removi=
ng state immediately (time =3D 0), wait for seconds or minutes, or do never re=
move the state (would be a bug indeed).=A0<BR>
<BR>
I personally would prefer to either give a fixed value or to give a formula=
 to calculate this time in a=A0standardised=A0way.=A0<BR>
<BR>
My proposal: Set this timer to 30 seconds fixed, as if there is no updating=
 CREATE or EXTERNAL message within 30 seconds to a 'transit' state there won=
't be anything beyond this anymore.<BR>
<BR>
=A0=A0Martin<BR>
<BR>
&nbsp;<BR>
stiemerling@netlab.nec.de<BR>
<BR>
NEC Laboratories Europe - Network Research Division<BR>
<BR>
NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014<BR>
&nbsp;<BR>
<BR>
<BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"></SPAN></FONT><FONT SIZE=3D"2"><FONT FA=
CE=3D"Monaco, Courier New"><SPAN STYLE=3D'font-size:10.0px'>____________________=
___________________________<BR>
nsis mailing list<BR>
nsis@ietf.org<BR>
https://www1.ietf.org/mailman/listinfo/nsis<BR>
</SPAN></FONT></FONT></BLOCKQUOTE><FONT SIZE=3D"2"><FONT FACE=3D"Monaco, Courie=
r New"><SPAN STYLE=3D'font-size:10.0px'><BR>
</SPAN></FONT></FONT>
</BODY>
</HTML>


--B_3284530649_2855303--




--===============0514157001==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0514157001==--






From nsis-bounces@ietf.org Wed Jan 30 03:37:50 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JK8S6-0001tZ-Eh; Wed, 30 Jan 2008 03:37:50 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JK8S4-0001qt-Lr
	for nsis-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 03:37:48 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JK8S4-0001ot-4b
	for nsis@ietf.org; Wed, 30 Jan 2008 03:37:48 -0500
Received: from smtp0.neclab.eu ([195.37.70.41])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JK8S3-0003TO-Ay
	for nsis@ietf.org; Wed, 30 Jan 2008 03:37:48 -0500
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id E4AE02C01D51A
	for <nsis@ietf.org>; Wed, 30 Jan 2008 09:37:46 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1])
	by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6LaKq0ADcKfp for <nsis@ietf.org>;
	Wed, 30 Jan 2008 09:37:46 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id C6A3E2C01D461
	for <nsis@ietf.org>; Wed, 30 Jan 2008 09:37:41 +0100 (CET)
Received: from 10.1.1.109 ([10.1.1.109]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Wed, 30 Jan 2008 08:37:42 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Wed, 30 Jan 2008 09:37:39 +0100
Subject: Re: [NSIS] NATFW issue: proxy flag handling
From: Martin Stiemerling <Stiemerling@nw.neclab.eu>
To: nsis <nsis@ietf.org>
Message-ID: <C3C5F5E3.EA14%Stiemerling@nw.neclab.eu>
Thread-Topic: [NSIS] NATFW issue: proxy flag handling
Thread-Index: AchjG18MneaR2s8OEdyTkgAWy5Ti1Q==
In-Reply-To: <1877E81B-5AE0-435C-AD64-92A273947A76@netlab.nec.de>
Mime-version: 1.0
X-Spam-Score: 1.8 (+)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1936293726=="
Errors-To: nsis-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1936293726==
Content-type: multipart/alternative;
	boundary="B_3284530660_2881333"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3284530660_2881333
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

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

Hi,

I do assume that everybody is fine with the proposed change.

If not, please speak up now!

Thanks,=20

  Martin (as NATFW NSLP author)


Am 24.01.2008 11:45 Uhr schrieb "Martin Stiemerling" unter
<stiemerling@netlab.nec.de>:

> [writing with chair's hat off, i.e., as NATFW NSLP author only!]
>=20
> Hi all,
>=20
> Section=A04.1. =A0"NSLP Header" also defines some processing for the proxy (p=
)
> flag and the different messages.=A0
> The text:
> The P flag indicates the usage of proxy mode. =A0If proxy mode is used
> it MUST be set to 1. =A0Proxy mode usage is only allowed in combination
> with the message types CREATE and EXTERNAL, P=3D1 MUST NOT be set with
> message types other than CREATE and EXTERNAL. =A0The P flag MUST be
> ignored when processing messages with type RESPONSE. =A0An 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.
>=20
> It's strange that the P flag must be ignored for RESPONSE but generates a=
n
> error for NOTIFY.=A0
>=20
>=20
> Change proposal:
> OLD:
> The P flag MUST be=A0ignored when processing messages with type RESPONSE. =A0=
An
> error RESPONSE message of class 'Protocol error' (0x3) and type 'Bad
> flags=A0value' (0x03) MUST be generated, if the P flag is set in NOTIFY=A0
>=20
> NEW:
> The P flag MUST be=A0ignored when processing messages with type RESPONSE an=
d
> NOTIFY.=A0
>=20
>=20
>=20
> The P flag is anyhow meaningless with those two message types.=A0
> =A0=A0
> =A0Martin
>=20
>=20
> =20
> stiemerling@netlab.nec.de
>=20
> NEC Laboratories Europe - Network Research Division
>=20
> NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, Londo=
n W3
> 6BL | Registered in England 2832014
> =20
>=20
>=20
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis



--B_3284530660_2881333
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [NSIS] NATFW issue: proxy flag handling</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'>[writ=
ing with chair's hat off, i.e., as NATFW NSLP author only!]<BR>
<BR>
Hi,<BR>
<BR>
I do assume that everybody is fine with the proposed change. <BR>
<BR>
If not, please speak up now!<BR>
<BR>
Thanks, <BR>
<BR>
&nbsp;&nbsp;Martin (as NATFW NSLP author)<BR>
<BR>
<BR>
Am 24.01.2008 11:45 Uhr schrieb &quot;Martin Stiemerling&quot; unter &lt;st=
iemerling@netlab.nec.de&gt;:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'>[writing with chair's hat off, i.e., as NATFW NSLP auth=
or only!]<BR>
<BR>
Hi all,<BR>
<BR>
Section=A04.1. =A0&quot;NSLP Header&quot; also defines some processing for the =
proxy (p) flag and the different messages.=A0<BR>
The text:<BR>
The P flag indicates the usage of proxy mode. =A0If proxy mode is used<BR>
it MUST be set to 1. =A0Proxy mode usage is only allowed in combination<BR>
with the message types CREATE and EXTERNAL, P=3D1 MUST NOT be set with<BR>
message types other than CREATE and EXTERNAL. =A0The P flag MUST be<BR>
ignored when processing messages with type RESPONSE. =A0An error<BR>
RESPONSE message of class 'Protocol error' (0x3) and type 'Bad flags<BR>
value' (0x03) MUST be generated, if the P flag is set in NOTIFY<BR>
messages.<BR>
<BR>
It's strange that the P flag must be ignored for RESPONSE but generates an =
error for NOTIFY.=A0<BR>
<BR>
<BR>
Change proposal:<BR>
OLD:<BR>
The P flag MUST be=A0ignored when processing messages with type RESPONSE. =A0An=
 error RESPONSE message of class 'Protocol error' (0x3) and type 'Bad flags=A0=
value' (0x03) MUST be generated, if the P flag is set in NOTIFY=A0<BR>
<BR>
NEW:<BR>
The P flag MUST be=A0ignored when processing messages with type RESPONSE and =
NOTIFY.=A0<BR>
<BR>
<BR>
<BR>
The P flag is anyhow meaningless with those two message types.=A0<BR>
=A0=A0<BR>
=A0Martin<BR>
<BR>
<BR>
&nbsp;<BR>
stiemerling@netlab.nec.de<BR>
<BR>
NEC Laboratories Europe - Network Research Division<BR>
<BR>
NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014<BR>
&nbsp;<BR>
<BR>
<BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"></SPAN></FONT><FONT SIZE=3D"2"><FONT FA=
CE=3D"Monaco, Courier New"><SPAN STYLE=3D'font-size:10.0px'>____________________=
___________________________<BR>
nsis mailing list<BR>
nsis@ietf.org<BR>
https://www1.ietf.org/mailman/listinfo/nsis<BR>
</SPAN></FONT></FONT></BLOCKQUOTE><FONT SIZE=3D"2"><FONT FACE=3D"Monaco, Courie=
r New"><SPAN STYLE=3D'font-size:10.0px'><BR>
</SPAN></FONT></FONT>
</BODY>
</HTML>


--B_3284530660_2881333--




--===============1936293726==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1936293726==--






From nsis-bounces@ietf.org Wed Jan 30 03:38:28 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JK8Si-0002Hs-B0; Wed, 30 Jan 2008 03:38:28 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JK8Sh-0002HL-BO
	for nsis-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 03:38:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JK8Sg-0002H7-Vt
	for nsis@ietf.org; Wed, 30 Jan 2008 03:38:26 -0500
Received: from smtp0.neclab.eu ([195.37.70.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JK8Sg-0002Y6-6B
	for nsis@ietf.org; Wed, 30 Jan 2008 03:38:26 -0500
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id C758C2C01D51A
	for <nsis@ietf.org>; Wed, 30 Jan 2008 09:38:25 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1])
	by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id c+eDghnfYDKj for <nsis@ietf.org>;
	Wed, 30 Jan 2008 09:38:25 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id A959B2C01D45F
	for <nsis@ietf.org>; Wed, 30 Jan 2008 09:38:20 +0100 (CET)
Received: from 10.1.1.109 ([10.1.1.109]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Wed, 30 Jan 2008 08:38:21 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Wed, 30 Jan 2008 09:38:19 +0100
Subject: Re: [NSIS] NATFW issue: Lifetime error messages
From: Martin Stiemerling <Stiemerling@nw.neclab.eu>
To: nsis <nsis@ietf.org>
Message-ID: <C3C5F60B.EA16%Stiemerling@nw.neclab.eu>
Thread-Topic: [NSIS] NATFW issue: Lifetime error messages
Thread-Index: AchjG3bktT1jK88OEdyTkgAWy5Ti1Q==
In-Reply-To: <23EEB316-B5AC-48B7-BC9B-373FB0BC51EA@netlab.nec.de>
Mime-version: 1.0
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1955107151=="
Errors-To: nsis-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============1955107151==
Content-type: multipart/alternative;
	boundary="B_3284530699_2837634"

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3284530699_2837634
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable


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

Hi,

I do assume that everybody is also fine with this proposed change.

If not, please speak up now!

Thanks,=20

  Martin (as NATFW NSLP author)

Am 24.01.2008 11:39 Uhr schrieb "Martin Stiemerling" unter
<stiemerling@netlab.nec.de>:

> [writing with chair's hat off, i.e., as NATFW NSLP author only!]
>=20
> Hi all,
>=20
> When reading Section=A03.4.=A0 Calculation of Signaling Session Lifetime I
> stumbled over the error messages send when NFs or the NR reject the sessi=
on
> lifetime.=A0
>=20
> Currently, there are two error codes (thus also cases) defined:
> 0x02: Requested lifetime is too big.
> 0x10: Requested lifetime is too small.
>=20
> These two error cases are used to tell the NI whether the requested lifet=
ime
> has an issue *and* if the by an NF/NR modified lifetime has an issue (see
> Section 3.4 before figure 12). This is a bit overloaded, as the NI eventu=
ally
> cannot tell whether his lifetime proposal was bad or if the en-route chan=
ged
> lifetime as bad.=A0
>=20
> My change proposal:
> Keep these error codes 0x02 and 0x10 for rejection of NI's lifetime propo=
sal
> and add two new error codes for rejection of a modified lifetime:
> 0xXY: Modified lifetime is too big.
> 0xSD: Modified lifetime is too small.
> (0xXY and 0xSD must be replaced by real number later on)
>=20
> Those messages are generated as an error response if one of the NFs or th=
e NR
> has changed in away that other NFs cannot accept it anymore. This, at lea=
st,
> gives the NI the hint that the NFs/NR on the way have some trouble on agr=
eeing
> a lifetime value.
>=20
>=20
> =A0=A0Martin
>=20
> =20
> stiemerling@netlab.nec.de
>=20
> NEC Laboratories Europe - Network Research Division
>=20
> NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, Londo=
n W3
> 6BL | Registered in England 2832014
> =20
>=20
>=20
>=20
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis



--B_3284530699_2837634
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [NSIS] NATFW issue: Lifetime error messages</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'><BR>
[writing with chair's hat off, i.e., as NATFW NSLP author only!]<BR>
<BR>
Hi,<BR>
<BR>
I do assume that everybody is also fine with this proposed change. <BR>
<BR>
If not, please speak up now!<BR>
<BR>
Thanks, <BR>
<BR>
&nbsp;&nbsp;Martin (as NATFW NSLP author)<BR>
<BR>
Am 24.01.2008 11:39 Uhr schrieb &quot;Martin Stiemerling&quot; unter &lt;st=
iemerling@netlab.nec.de&gt;:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'>[writing with chair's hat off, i.e., as NATFW NSLP auth=
or only!]<BR>
<BR>
Hi all,<BR>
<BR>
When reading Section=A03.4.=A0 Calculation of Signaling Session Lifetime I stum=
bled over the error messages send when NFs or the NR reject the session life=
time.=A0<BR>
<BR>
Currently, there are two error codes (thus also cases) defined:<BR>
0x02: Requested lifetime is too big.<BR>
0x10: Requested lifetime is too small.<BR>
<BR>
These two error cases are used to tell the NI whether the requested lifetim=
e has an issue *and* if the by an NF/NR modified lifetime has an issue (see =
Section 3.4 before figure 12). This is a bit overloaded, as the NI eventuall=
y cannot tell whether his lifetime proposal was bad or if the en-route chang=
ed lifetime as bad.=A0<BR>
<BR>
My change proposal:<BR>
Keep these error codes 0x02 and 0x10 for rejection of NI's lifetime proposa=
l and add two new error codes for rejection of a modified lifetime:<BR>
0xXY: Modified lifetime is too big.<BR>
0xSD: Modified lifetime is too small.<BR>
(0xXY and 0xSD must be replaced by real number later on)<BR>
<BR>
Those messages are generated as an error response if one of the NFs or the =
NR has changed in away that other NFs cannot accept it anymore. This, at lea=
st, gives the NI the hint that the NFs/NR on the way have some trouble on ag=
reeing a lifetime value.<BR>
<BR>
<BR>
=A0=A0Martin<BR>
<BR>
&nbsp;<BR>
stiemerling@netlab.nec.de<BR>
<BR>
NEC Laboratories Europe - Network Research Division<BR>
<BR>
NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014<BR>
&nbsp;<BR>
<BR>
<BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"></SPAN></FONT><FONT SIZE=3D"2"><FONT FA=
CE=3D"Monaco, Courier New"><SPAN STYLE=3D'font-size:10.0px'>____________________=
___________________________<BR>
nsis mailing list<BR>
nsis@ietf.org<BR>
https://www1.ietf.org/mailman/listinfo/nsis<BR>
</SPAN></FONT></FONT></BLOCKQUOTE><FONT SIZE=3D"2"><FONT FACE=3D"Monaco, Courie=
r New"><SPAN STYLE=3D'font-size:10.0px'><BR>
</SPAN></FONT></FONT>
</BODY>
</HTML>


--B_3284530699_2837634--




--===============1955107151==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1955107151==--






From nsis-bounces@ietf.org Wed Jan 30 03:42:21 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JK8WT-0005Hk-36; Wed, 30 Jan 2008 03:42:21 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JK8WQ-00059B-GK
	for nsis-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 03:42:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JK8WN-00053u-2K
	for nsis@ietf.org; Wed, 30 Jan 2008 03:42:15 -0500
Received: from mail.gmx.net ([213.165.64.20])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1JK8WM-0002eK-87
	for nsis@ietf.org; Wed, 30 Jan 2008 03:42:15 -0500
Received: (qmail invoked by alias); 30 Jan 2008 08:42:12 -0000
Received: from proxy4-nsn.nsn-inter.net (EHLO [217.115.75.232])
	[217.115.75.232]
	by mail.gmx.net (mp053) with SMTP; 30 Jan 2008 09:42:12 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+JHecbk3aJfSYzq4hkaBqFHwr/tg8SUm9fQdZsrB
	136qqhtISSiXOk
Message-ID: <47A03867.4050101@gmx.net>
Date: Wed, 30 Jan 2008 10:42:15 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Martin Stiemerling <Stiemerling@nw.neclab.eu>
Subject: Re: [NSIS] NATFW issue: state 'transit' timer definition
References: <C3C5F5D9.EA12%Stiemerling@nw.neclab.eu>
In-Reply-To: <C3C5F5D9.EA12%Stiemerling@nw.neclab.eu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: nsis <nsis@ietf.org>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org

Setting the default value to 30 seconds sounds fine to me.

Ciao
Hannes

Martin Stiemerling wrote:
> [writing with chair's hat off, i.e., as NATFW NSLP author only!]
>
> Hi,
>
> I do assume that everybody is fine with the proposed change.
>
> If not, please speak up now!
>
> Thanks, 
>
>   Martin (as NATFW NSLP author)
>
>
> Am 24.01.2008 11:22 Uhr schrieb "Martin Stiemerling" unter
> <stiemerling@netlab.nec.de>:
>
>   
>> [writing with chair's hat off, i.e., as NATFW NSLP author only!]
>>
>> Hi all,
>>
>> I finally found time to get back to the NATFW NSLP and your WGLC comments.
>> Thanks to all who did a review and sent in their comments!
>>
>> I also have done a complete review of draft-ietf-nsis-nslp-natfw-16.txt and
>> found some issues to be discussed. There will be separate e-mails for each
>> issue I've found. 
>>
>> Here we go:
>>
>> In Section 3.2.8.  NATFW NSLP Signaling Sessions the different conceptual
>> states of the a NATFW NSLP signaling session are defined. I see all states are
>> fine except the last one which is 'transit':
>>
>> Transit: The node has received an asynchronous message, i.e., a
>> NOTIFY, and can delete the NATFW NSLP signaling session if needed.
>> When a node has received a NOTIFY message (for instance,
>> indicating a route change) it marks it as 'Transit' and deletes
>> this NATFW NSLP signaling session if it is unused for some time
>> specific to the local node.  This idle time does not need to be
>> fixed, since it can depend on the node local maintenance cycle,
>> i.e., the NATFW NSLP signaling session could be deleted if the
>> node runs it garbage collection cycle.
>>
>> The issue is see, is the undefined timer value in this state. It simply says
>> "...for some time..." which can result in implementations removing state
>> immediately (time = 0), wait for seconds or minutes, or do never remove the
>> state (would be a bug indeed). 
>>
>> I personally would prefer to either give a fixed value or to give a formula to
>> calculate this time in a standardised way. 
>>
>> My proposal: Set this timer to 30 seconds fixed, as if there is no updating
>> CREATE or EXTERNAL message within 30 seconds to a 'transit' state there won't
>> be anything beyond this anymore.
>>
>>   Martin
>>
>>  
>> stiemerling@netlab.nec.de
>>
>> 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
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
>>     
>
>
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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



From nsis-bounces@ietf.org Wed Jan 30 03:45:10 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JK8ZC-0003uj-LG; Wed, 30 Jan 2008 03:45:10 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JK8ZA-0003qq-0w
	for nsis-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 03:45:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JK8Z9-0003qi-NQ
	for nsis@ietf.org; Wed, 30 Jan 2008 03:45:07 -0500
Received: from mail.gmx.net ([213.165.64.20])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1JK8Z9-0002ht-4o
	for nsis@ietf.org; Wed, 30 Jan 2008 03:45:07 -0500
Received: (qmail invoked by alias); 30 Jan 2008 08:45:06 -0000
Received: from proxy4-nsn.nsn-inter.net (EHLO [217.115.75.232])
	[217.115.75.232]
	by mail.gmx.net (mp047) with SMTP; 30 Jan 2008 09:45:06 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1//MnFombn/0mKmcVoZUvYCDUIdRfKNLcmnijEIPn
	Gcf5XqmTdW48qM
Message-ID: <47A03915.60008@gmx.net>
Date: Wed, 30 Jan 2008 10:45:09 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Martin Stiemerling <Stiemerling@nw.neclab.eu>
Subject: Re: [NSIS] NATFW issue: proxy flag handling
References: <C3C5F5E3.EA14%Stiemerling@nw.neclab.eu>
In-Reply-To: <C3C5F5E3.EA14%Stiemerling@nw.neclab.eu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: nsis <nsis@ietf.org>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org

Hi Martin,

I am fine with the suggested change.

I wonder whether we should also remove the following statement:
"
P=1 MUST NOT be set with message types other than CREATE and EXTERNAL.

"

We essentially list the messages where the proxy flag is allowed and where it is ignored. 
We shouldn't say anything about messages that aren't defined in the document since this might harm extensibility later.

Ciao
Hannes


Martin Stiemerling wrote:
> [writing with chair's hat off, i.e., as NATFW NSLP author only!]
>
> Hi,
>
> I do assume that everybody is fine with the proposed change.
>
> If not, please speak up now!
>
> Thanks, 
>
>   Martin (as NATFW NSLP author)
>
>
> Am 24.01.2008 11:45 Uhr schrieb "Martin Stiemerling" unter
> <stiemerling@netlab.nec.de>:
>
>   
>> [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
>>
>>
>>  
>> stiemerling@netlab.nec.de
>>
>> 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
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
>>     
>
>
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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



From nsis-bounces@ietf.org Wed Jan 30 03:47:24 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JK8bL-0005Ia-QA; Wed, 30 Jan 2008 03:47:23 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JK8bK-0005Gm-DJ
	for nsis-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 03:47:22 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JK8bK-0005Gd-25
	for nsis@ietf.org; Wed, 30 Jan 2008 03:47:22 -0500
Received: from mail.gmx.net ([213.165.64.20])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1JK8bJ-0003k8-8N
	for nsis@ietf.org; Wed, 30 Jan 2008 03:47:21 -0500
Received: (qmail invoked by alias); 30 Jan 2008 08:47:19 -0000
Received: from proxy4-nsn.nsn-inter.net (EHLO [217.115.75.232])
	[217.115.75.232]
	by mail.gmx.net (mp043) with SMTP; 30 Jan 2008 09:47:19 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19SGOsoosNSlIiVFhW7nkJewi6zIkMMUUIEfrw8/h
	4HTt9BV/9nQspL
Message-ID: <47A0399B.1030104@gmx.net>
Date: Wed, 30 Jan 2008 10:47:23 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Martin Stiemerling <Stiemerling@nw.neclab.eu>
Subject: Re: [NSIS] NATFW issue: Lifetime error messages
References: <C3C5F60B.EA16%Stiemerling@nw.neclab.eu>
In-Reply-To: <C3C5F60B.EA16%Stiemerling@nw.neclab.eu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: nsis <nsis@ietf.org>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org

I am OK with the suggested change. Adding two error codes to make the 
situation clearer seems to be a good idea.

Ciao
Hannes

Martin Stiemerling wrote:
> [writing with chair's hat off, i.e., as NATFW NSLP author only!]
>
> Hi,
>
> I do assume that everybody is also fine with this proposed change.
>
> If not, please speak up now!
>
> Thanks, 
>
>   Martin (as NATFW NSLP author)
>
> Am 24.01.2008 11:39 Uhr schrieb "Martin Stiemerling" unter
> <stiemerling@netlab.nec.de>:
>
>   
>> [writing with chair's hat off, i.e., as NATFW NSLP author only!]
>>
>> Hi all,
>>
>> When reading Section 3.4.  Calculation of Signaling Session Lifetime I
>> stumbled over the error messages send when NFs or the NR reject the session
>> lifetime. 
>>
>> Currently, there are two error codes (thus also cases) defined:
>> 0x02: Requested lifetime is too big.
>> 0x10: Requested lifetime is too small.
>>
>> These two error cases are used to tell the NI whether the requested lifetime
>> has an issue *and* if the by an NF/NR modified lifetime has an issue (see
>> Section 3.4 before figure 12). This is a bit overloaded, as the NI eventually
>> cannot tell whether his lifetime proposal was bad or if the en-route changed
>> lifetime as bad. 
>>
>> My change proposal:
>> Keep these error codes 0x02 and 0x10 for rejection of NI's lifetime proposal
>> and add two new error codes for rejection of a modified lifetime:
>> 0xXY: Modified lifetime is too big.
>> 0xSD: Modified lifetime is too small.
>> (0xXY and 0xSD must be replaced by real number later on)
>>
>> Those messages are generated as an error response if one of the NFs or the NR
>> has changed in away that other NFs cannot accept it anymore. This, at least,
>> gives the NI the hint that the NFs/NR on the way have some trouble on agreeing
>> a lifetime value.
>>
>>
>>   Martin
>>
>>  
>> stiemerling@netlab.nec.de
>>
>> 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
>> nsis@ietf.org
>> https://www1.ietf.org/mailman/listinfo/nsis
>>     
>
>
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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



From nsis-bounces@ietf.org Wed Jan 30 03:55:24 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JK8j5-0000Cj-AN; Wed, 30 Jan 2008 03:55:23 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JK8j4-0000Ce-LY
	for nsis-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 03:55:22 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JK8j3-0000CQ-2S
	for nsis@ietf.org; Wed, 30 Jan 2008 03:55:22 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JK8j2-0003vQ-5N
	for nsis@ietf.org; Wed, 30 Jan 2008 03:55:20 -0500
Received: from ewi977 (ewi977.ewi.utwente.nl [130.89.12.129])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	m0U8tFnA020054; Wed, 30 Jan 2008 09:55:18 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Martin Stiemerling'" <Stiemerling@nw.neclab.eu>, "'nsis'" <nsis@ietf.org>
References: <5B37E709-9B27-4490-B2EF-FAB14235153E@netlab.nec.de>
	<C3C5F5D9.EA12%Stiemerling@nw.neclab.eu>
Subject: RE: [NSIS] NATFW issue: state 'transit' timer definition
Date: Wed, 30 Jan 2008 09:55:09 +0100
Message-ID: <003401c8631d$d43a2180$810c5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <C3C5F5D9.EA12%Stiemerling@nw.neclab.eu>
Thread-Index: AchjG1kWl7hu2s8OEdyTkgAWy5Ti1QAAlmbQ
X-Spam-Score: 0.528 () HTML_40_50,HTML_MESSAGE
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Wed, 30 Jan 2008 09:55:19 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 325b777e1a3a618c889460b612a65510
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1931971422=="
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1931971422==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0035_01C86326.35FE8980"

This is a multi-part message in MIME format.

------=_NextPart_000_0035_01C86326.35FE8980
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Martin 
 
A default value of 30 seconds for the timer is fine for me!
 
Best regards,
Georgios
 


  _____  

From: Martin Stiemerling [mailto:Stiemerling@nw.neclab.eu] 
Sent: woensdag 30 januari 2008 9:37
To: nsis
Subject: Re: [NSIS] NATFW issue: state 'transit' timer definition


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

Hi,

I do assume that everybody is fine with the proposed change. 

If not, please speak up now!

Thanks, 

  Martin (as NATFW NSLP author)


Am 24.01.2008 11:22 Uhr schrieb "Martin Stiemerling" unter
<stiemerling@netlab.nec.de>:



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

Hi all,

I finally found time to get back to the NATFW NSLP and your WGLC comments.
Thanks to all who did a review and sent in their comments!

I also have done a complete review of draft-ietf-nsis-nslp-natfw-16.txt and
found some issues to be discussed. There will be separate e-mails for each
issue I've found. 

Here we go:

In Section 3.2.8.  NATFW NSLP Signaling Sessions the different conceptual
states of the a NATFW NSLP signaling session are defined. I see all states
are fine except the last one which is 'transit':

Transit: The node has received an asynchronous message, i.e., a
NOTIFY, and can delete the NATFW NSLP signaling session if needed.
When a node has received a NOTIFY message (for instance,
indicating a route change) it marks it as 'Transit' and deletes
this NATFW NSLP signaling session if it is unused for some time
specific to the local node.  This idle time does not need to be
fixed, since it can depend on the node local maintenance cycle,
i.e., the NATFW NSLP signaling session could be deleted if the
node runs it garbage collection cycle.

The issue is see, is the undefined timer value in this state. It simply says
"...for some time..." which can result in implementations removing state
immediately (time = 0), wait for seconds or minutes, or do never remove the
state (would be a bug indeed). 

I personally would prefer to either give a fixed value or to give a formula
to calculate this time in a standardised way. 

My proposal: Set this timer to 30 seconds fixed, as if there is no updating
CREATE or EXTERNAL message within 30 seconds to a 'transit' state there
won't be anything beyond this anymore.

  Martin

 
stiemerling@netlab.nec.de

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
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis






------=_NextPart_000_0035_01C86326.35FE8980
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Re: [NSIS] NATFW issue: state 'transit' timer =
definition</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16587" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D342185408-30012008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Martin </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D342185408-30012008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D342185408-30012008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>A default value of 30 seconds for the timer is =
fine for=20
me!</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D342185408-30012008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D342185408-30012008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Best regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D342185408-30012008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Georgios</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D342185408-30012008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Martin Stiemerling=20
  [mailto:Stiemerling@nw.neclab.eu] <BR><B>Sent:</B> woensdag 30 januari =
2008=20
  9:37<BR><B>To:</B> nsis<BR><B>Subject:</B> Re: [NSIS] NATFW issue: =
state=20
  'transit' timer definition<BR></FONT><BR></DIV>
  <DIV></DIV><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
  style=3D"FONT-SIZE: 12px">[writing with chair's hat off, i.e., as =
NATFW NSLP=20
  author only!]<BR><BR>Hi,<BR><BR>I do assume that everybody is fine =
with the=20
  proposed change. <BR><BR>If not, please speak up now!<BR><BR>Thanks,=20
  <BR><BR>&nbsp;&nbsp;Martin (as NATFW NSLP author)<BR><BR><BR>Am =
24.01.2008=20
  11:22 Uhr schrieb "Martin Stiemerling" unter=20
  &lt;stiemerling@netlab.nec.de&gt;:<BR><BR></SPAN></FONT>
  <BLOCKQUOTE><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
    style=3D"FONT-SIZE: 12px">[writing with chair's hat off, i.e., as =
NATFW NSLP=20
    author only!]<BR><BR>Hi all,<BR><BR>I finally found time to get back =
to the=20
    NATFW NSLP and your WGLC comments. Thanks to all who did a review =
and sent=20
    in their comments!<BR><BR>I also have done a complete review=20
    of&nbsp;draft-ietf-nsis-nslp-natfw-16.txt and found some issues to =
be=20
    discussed. There will be separate e-mails for each issue I've=20
    found.&nbsp;<BR><BR>Here we go:<BR><BR>In Section&nbsp;3.2.8.&nbsp; =
NATFW=20
    NSLP Signaling Sessions the different conceptual states of the a =
NATFW NSLP=20
    signaling session are defined. I see all states are fine except the =
last one=20
    which is 'transit':<BR><BR>Transit: The node has received an =
asynchronous=20
    message, i.e., a<BR>NOTIFY, and can delete the NATFW NSLP signaling =
session=20
    if needed.<BR>When a node has received a NOTIFY message (for=20
    instance,<BR>indicating a route change) it marks it as 'Transit' and =

    deletes<BR>this NATFW NSLP signaling session if it is unused for =
some=20
    time<BR>specific to the local node. &nbsp;This idle time does not =
need to=20
    be<BR>fixed, since it can depend on the node local maintenance=20
    cycle,<BR>i.e., the NATFW NSLP signaling session could be deleted if =

    the<BR>node runs it garbage collection cycle.<BR><BR>The issue is =
see, is=20
    the undefined timer value in this state. It simply says "...for some =

    time..." which can result in implementations removing state =
immediately=20
    (time =3D 0), wait for seconds or minutes, or do never remove the =
state (would=20
    be a bug indeed).&nbsp;<BR><BR>I personally would prefer to either =
give a=20
    fixed value or to give a formula to calculate this time in=20
    a&nbsp;standardised&nbsp;way.&nbsp;<BR><BR>My proposal: Set this =
timer to 30=20
    seconds fixed, as if there is no updating CREATE or EXTERNAL message =
within=20
    30 seconds to a 'transit' state there won't be anything beyond this=20
    =
anymore.<BR><BR>&nbsp;&nbsp;Martin<BR><BR>&nbsp;<BR>stiemerling@netlab.ne=
c.de<BR><BR>NEC=20
    Laboratories Europe - Network Research Division<BR><BR>NEC Europe =
Limited |=20
    Registered Office: NEC House, 1 Victoria Road, London W3 6BL | =
Registered in=20
    England 2832014<BR>&nbsp;<BR><BR><BR>
    <HR align=3Dcenter width=3D"95%" SIZE=3D3>
    </SPAN></FONT><FONT size=3D2><FONT face=3D"Monaco, Courier =
New"><SPAN=20
    style=3D"FONT-SIZE: =
10px">_______________________________________________<BR>nsis=20
    mailing=20
    =
list<BR>nsis@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/nsis<BR><=
/SPAN></FONT></FONT></BLOCKQUOTE><FONT=20
  size=3D2><FONT face=3D"Monaco, Courier New"><SPAN=20
style=3D"FONT-SIZE: =
10px"><BR></BLOCKQUOTE></SPAN></FONT></FONT></BODY></HTML>

------=_NextPart_000_0035_01C86326.35FE8980--





--===============1931971422==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1931971422==--







From nsis-bounces@ietf.org Wed Jan 30 03:58:06 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JK8lg-0001HM-Dj; Wed, 30 Jan 2008 03:58:04 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JK8lf-0001HG-0q
	for nsis-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 03:58:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JK8le-0001H8-ND
	for nsis@ietf.org; Wed, 30 Jan 2008 03:58:02 -0500
Received: from rotterdam.ewi.utwente.nl ([130.89.10.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JK8ld-0002vG-Lv
	for nsis@ietf.org; Wed, 30 Jan 2008 03:58:02 -0500
Received: from ewi977 (ewi977.ewi.utwente.nl [130.89.12.129])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	m0U8vvZI020947; Wed, 30 Jan 2008 09:58:00 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Martin Stiemerling'" <Stiemerling@nw.neclab.eu>, "'nsis'" <nsis@ietf.org>
References: <23EEB316-B5AC-48B7-BC9B-373FB0BC51EA@netlab.nec.de>
	<C3C5F60B.EA16%Stiemerling@nw.neclab.eu>
Subject: RE: [NSIS] NATFW issue: Lifetime error messages
Date: Wed, 30 Jan 2008 09:57:51 +0100
Message-ID: <003901c8631e$35015e70$810c5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <C3C5F60B.EA16%Stiemerling@nw.neclab.eu>
Thread-Index: AchjG3bktT1jK88OEdyTkgAWy5Ti1QAApIgQ
X-Spam-Score: 0.528 () HTML_40_50,HTML_MESSAGE
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Wed, 30 Jan 2008 09:58:01 +0100 (MET)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c
Cc: 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0630006631=="
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0630006631==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_003A_01C86326.96C5C670"

This is a multi-part message in MIME format.

------=_NextPart_000_003A_01C86326.96C5C670
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Martin
 
I think that the two additional error codes are useful for clarification
purposes!
 
Best regards,
Georgios
 


  _____  

From: Martin Stiemerling [mailto:Stiemerling@nw.neclab.eu] 
Sent: woensdag 30 januari 2008 9:38
To: nsis
Subject: Re: [NSIS] NATFW issue: Lifetime error messages



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

Hi,

I do assume that everybody is also fine with this proposed change. 

If not, please speak up now!

Thanks, 

  Martin (as NATFW NSLP author)

Am 24.01.2008 11:39 Uhr schrieb "Martin Stiemerling" unter
<stiemerling@netlab.nec.de>:



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

Hi all,

When reading Section 3.4.  Calculation of Signaling Session Lifetime I
stumbled over the error messages send when NFs or the NR reject the session
lifetime. 

Currently, there are two error codes (thus also cases) defined:
0x02: Requested lifetime is too big.
0x10: Requested lifetime is too small.

These two error cases are used to tell the NI whether the requested lifetime
has an issue *and* if the by an NF/NR modified lifetime has an issue (see
Section 3.4 before figure 12). This is a bit overloaded, as the NI
eventually cannot tell whether his lifetime proposal was bad or if the
en-route changed lifetime as bad. 

My change proposal:
Keep these error codes 0x02 and 0x10 for rejection of NI's lifetime proposal
and add two new error codes for rejection of a modified lifetime:
0xXY: Modified lifetime is too big.
0xSD: Modified lifetime is too small.
(0xXY and 0xSD must be replaced by real number later on)

Those messages are generated as an error response if one of the NFs or the
NR has changed in away that other NFs cannot accept it anymore. This, at
least, gives the NI the hint that the NFs/NR on the way have some trouble on
agreeing a lifetime value.


  Martin

 
stiemerling@netlab.nec.de

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
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis






------=_NextPart_000_003A_01C86326.96C5C670
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Re: [NSIS] NATFW issue: Lifetime error =
messages</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16587" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D165435608-30012008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Martin</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D165435608-30012008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D165435608-30012008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I think that the two additional error codes are =
useful for=20
clarification purposes!</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D165435608-30012008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D165435608-30012008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Best regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D165435608-30012008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Georgios</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D165435608-30012008></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Martin Stiemerling=20
  [mailto:Stiemerling@nw.neclab.eu] <BR><B>Sent:</B> woensdag 30 januari =
2008=20
  9:38<BR><B>To:</B> nsis<BR><B>Subject:</B> Re: [NSIS] NATFW issue: =
Lifetime=20
  error messages<BR></FONT><BR></DIV>
  <DIV></DIV><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
  style=3D"FONT-SIZE: 12px"><BR>[writing with chair's hat off, i.e., as =
NATFW NSLP=20
  author only!]<BR><BR>Hi,<BR><BR>I do assume that everybody is also =
fine with=20
  this proposed change. <BR><BR>If not, please speak up =
now!<BR><BR>Thanks,=20
  <BR><BR>&nbsp;&nbsp;Martin (as NATFW NSLP author)<BR><BR>Am 24.01.2008 =
11:39=20
  Uhr schrieb "Martin Stiemerling" unter=20
  &lt;stiemerling@netlab.nec.de&gt;:<BR><BR></SPAN></FONT>
  <BLOCKQUOTE><FONT face=3D"Verdana, Helvetica, Arial"><SPAN=20
    style=3D"FONT-SIZE: 12px">[writing with chair's hat off, i.e., as =
NATFW NSLP=20
    author only!]<BR><BR>Hi all,<BR><BR>When reading =
Section&nbsp;3.4.&nbsp;=20
    Calculation of Signaling Session Lifetime I stumbled over the error =
messages=20
    send when NFs or the NR reject the session =
lifetime.&nbsp;<BR><BR>Currently,=20
    there are two error codes (thus also cases) defined:<BR>0x02: =
Requested=20
    lifetime is too big.<BR>0x10: Requested lifetime is too =
small.<BR><BR>These=20
    two error cases are used to tell the NI whether the requested =
lifetime has=20
    an issue *and* if the by an NF/NR modified lifetime has an issue =
(see=20
    Section 3.4 before figure 12). This is a bit overloaded, as the NI=20
    eventually cannot tell whether his lifetime proposal was bad or if =
the=20
    en-route changed lifetime as bad.&nbsp;<BR><BR>My change =
proposal:<BR>Keep=20
    these error codes 0x02 and 0x10 for rejection of NI's lifetime =
proposal and=20
    add two new error codes for rejection of a modified =
lifetime:<BR>0xXY:=20
    Modified lifetime is too big.<BR>0xSD: Modified lifetime is too=20
    small.<BR>(0xXY and 0xSD must be replaced by real number later=20
    on)<BR><BR>Those messages are generated as an error response if one =
of the=20
    NFs or the NR has changed in away that other NFs cannot accept it =
anymore.=20
    This, at least, gives the NI the hint that the NFs/NR on the way =
have some=20
    trouble on agreeing a lifetime=20
    =
value.<BR><BR><BR>&nbsp;&nbsp;Martin<BR><BR>&nbsp;<BR>stiemerling@netlab.=
nec.de<BR><BR>NEC=20
    Laboratories Europe - Network Research Division<BR><BR>NEC Europe =
Limited |=20
    Registered Office: NEC House, 1 Victoria Road, London W3 6BL | =
Registered in=20
    England 2832014<BR>&nbsp;<BR><BR><BR>
    <HR align=3Dcenter width=3D"95%" SIZE=3D3>
    </SPAN></FONT><FONT size=3D2><FONT face=3D"Monaco, Courier =
New"><SPAN=20
    style=3D"FONT-SIZE: =
10px">_______________________________________________<BR>nsis=20
    mailing=20
    =
list<BR>nsis@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/nsis<BR><=
/SPAN></FONT></FONT></BLOCKQUOTE><FONT=20
  size=3D2><FONT face=3D"Monaco, Courier New"><SPAN=20
style=3D"FONT-SIZE: =
10px"><BR></BLOCKQUOTE></SPAN></FONT></FONT></BODY></HTML>

------=_NextPart_000_003A_01C86326.96C5C670--





--===============0630006631==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0630006631==--







From nsis-bounces@ietf.org Wed Jan 30 03:58:14 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JK8lq-0001La-OQ; Wed, 30 Jan 2008 03:58:14 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JK8lp-0001LC-I6
	for nsis-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 03:58:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JK8lo-0001L4-I4
	for nsis@ietf.org; Wed, 30 Jan 2008 03:58:13 -0500
Received: from smtp0.neclab.eu ([195.37.70.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JK8ln-0002vS-St
	for nsis@ietf.org; Wed, 30 Jan 2008 03:58:12 -0500
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 759502C01D51A;
	Wed, 30 Jan 2008 09:58:11 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1])
	by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 72amjiVhv-ai; Wed, 30 Jan 2008 09:58:11 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 61C1B2C01D45F;
	Wed, 30 Jan 2008 09:58:01 +0100 (CET)
Received: from 10.1.1.109 ([10.1.1.109]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Wed, 30 Jan 2008 08:58:01 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Wed, 30 Jan 2008 09:57:59 +0100
Subject: Re: [NSIS] NATFW issue: proxy flag handling
From: Martin Stiemerling <Stiemerling@nw.neclab.eu>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Message-ID: <C3C5FAA7.EA2B%Stiemerling@nw.neclab.eu>
Thread-Topic: [NSIS] NATFW issue: proxy flag handling
Thread-Index: AchjHjY6dIPFTs8REdyTkgAWy5Ti1Q==
In-Reply-To: <47A03915.60008@gmx.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: nsis <nsis@ietf.org>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org

Hi Hannes,

You're right the sentence below can be safely removed.

Fixed.

Thanks,

  Martin


Am 30.01.2008 9:45 Uhr schrieb "Hannes Tschofenig" unter
<Hannes.Tschofenig@gmx.net>:

> Hi Martin,
> 
> I am fine with the suggested change.
> 
> I wonder whether we should also remove the following statement:
> "
> P=1 MUST NOT be set with message types other than CREATE and EXTERNAL.
> 
> "
> 
> We essentially list the messages where the proxy flag is allowed and where it
> is ignored. 
> We shouldn't say anything about messages that aren't defined in the document
> since this might harm extensibility later.
> 
> Ciao
> Hannes
> 
> 
> Martin Stiemerling wrote:
>> [writing with chair's hat off, i.e., as NATFW NSLP author only!]
>> 
>> Hi,
>> 
>> I do assume that everybody is fine with the proposed change.
>> 
>> If not, please speak up now!
>> 
>> Thanks, 
>> 
>>   Martin (as NATFW NSLP author)
>> 
>> 
>> Am 24.01.2008 11:45 Uhr schrieb "Martin Stiemerling" unter
>> <stiemerling@netlab.nec.de>:
>> 
>>   
>>> [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
>>> 
>>> 
>>>  
>>> stiemerling@netlab.nec.de
>>> 
>>> 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
>>> nsis@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/nsis
>>>     
>> 
>> 
>> 
>>   
>> ------------------------------------------------------------------------
>> 
>> _______________________________________________
>> 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



From nsis-bounces@ietf.org Wed Jan 30 06:20:39 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JKAzY-0005FP-Ba; Wed, 30 Jan 2008 06:20:32 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JKAzX-0005FK-BX
	for nsis-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 06:20:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JKAzX-0005FC-1j
	for nsis@ietf.org; Wed, 30 Jan 2008 06:20:31 -0500
Received: from smtp0.neclab.eu ([195.37.70.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JKAzV-0005rw-NP
	for nsis@ietf.org; Wed, 30 Jan 2008 06:20:31 -0500
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 4A95F2C002B48;
	Wed, 30 Jan 2008 12:20:29 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1])
	by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9fbA5HAf79Wb; Wed, 30 Jan 2008 12:20:29 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 24E672C000357;
	Wed, 30 Jan 2008 12:20:14 +0100 (CET)
Received: from 10.1.1.109 ([10.1.1.109]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Wed, 30 Jan 2008 11:20:11 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Wed, 30 Jan 2008 12:20:12 +0100
From: Martin Stiemerling <Stiemerling@nw.neclab.eu>
To: nsis <nsis@ietf.org>, <gash5107@yahoo.com>,
	<cornelia.kappler@googlemail.com>
Message-ID: <C3C61BFC.EA3F%Stiemerling@nw.neclab.eu>
Thread-Topic: Review of draft-ietf-nsis-qspec-18.txt
Thread-Index: AchjMhRKUvU/Ac8lEdybRgAWy5Ti1Q==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 76c7db407a166e4c39f35d8215d8dd32
Cc: 
Subject: [NSIS] Review of draft-ietf-nsis-qspec-18.txt
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org

Hi all,

Please find my review of draft-ietf-nsis-qspec-18.txt.

There are some minor technical issues to fix. In general the document seems
to be ready to go for AD review,  once the editorials and technical issues
have been fixed.

Please address the issues and submit an updated version of the draft if d
one so. I will go ahead with the updated draft for the protocol write up
(i.e., the step before sending to Magnus and the IESG).

  Martin

****
General
****
I found the first part of the document (i.e., until section 5) quite
confusing and after section five quite clear. This does not mean that there
is an issue, as typically Internet drafts have the need to sketch tech
things in the beginning without having the reader already at the technical
level. I assume that the text is fine right now, as the WG has not pushed to
change it.



****
Editorial:
****

- the idnits tool has found some issues (see below)
- Add line in memo heading with: Intended Status: Informational
-  Section 1: Move to the very end of memo. It it is good to acknowledge
other people, but it is fair enough to do it at the very end, as technical
protocol stuff comes first.
- section 2: Adding a line saying that QSPEC readers should (or better
must?) read the QoS NSLP in advance would be advantageous for the whole
document. 
- section 2, page 5, para starting with "Interoperability between QoS NSIS
entities (QNEs)..." says that parameters can be flagged or not flagged. I
suggest to put the terms "flagged"/"non flagged" in brackets and write
mandatory and optional parameters. This makes it easier for first time
readers. 
- - section 2, page 5, para starting with " A local QSPEC can be defined in
a local domain with the initiator QSPEC encapsulated, ...". This paragraph
is brief but describes a very powerful mechanism of the QSPEC. I would
suggest to remove the hint the TMOD parameter and just write that the QSPEC
allows local QPSECs that are domain specific. This also helps first time
readers to understand a basic feature of  QPSEC but not the full
implementation of it.
- section 4.1, 2nd para, text in para starting with " New QoS NSLP message
processing rules can only be defined in Standard...". Is it required to say
this at this part of the document at all? I remember this again stated in
the document somewhere later on at an appropriate place.
- section 4.2 two paras below figure 1. Suddenly there is text about RESERVE
and QUERY, but no hint to the QoS NSLP at all. Adding a reference to the QoS
NSLP at this occasion would be excellent. Otherwise it  is hard to see where
those terms are coming from
- section 4.3.1, para starting with " When the TMOD parameter in included in
QoS Available, it..." should read " When the TMOD parameter are included in
QoS Available, it..."
- section 4.3.1. This section nevers talks about tmod-2! tmod-2 is
mentioned only  in sections 6.2.1 and 6.2.2.
- section 5, 1st and 2nd para suddenly use the E-/N-flag without every
explaining their meaning.
- section 5.1, again the support of local QSPECs is quite powerful but never
really good explained with a figure. For instance, the first para of section
5.1 could refer to a simple figure showing a network configuration for a
single flow, but with indications where which QSPEC is used. This instantly
makes the whole concept better undestandable.
- section 5.2.5. formatting error
- section 5.3.1 and related. You use tables to define cases and also refer
to them later in the object definition. Thus it would be good to label those
tables.
- section 5.3.5 has one formatting issue and one spelling error (s/described
In [QoS-SIG]/ described in [QoS-SIG])
- section 5.4. remove reference to NSIS extensibility document, as we do not
have it ready by now.
- section 6.1. I got confused by all the different header definition. I
would propose to split 6.1. in subsections, i.e., one for each header
definition. This improves readability.
- section 6.2.1: Why is there this line    <TMOD-1> = <r> <b> <p> <m>
[RFC2210, RFC2215]? It is now required for the object definition.
- section 8, text says " Object Types (12 bits):" but should read "QSPEC
Object Types (12 bits):".
- appendix b: add a note in the first line that this appendix should be
removed by the RFC editor before publication.



***
Technical
***
- section 5.3.1, para starting with " The QSPEC parameter IDs and values
included in the QoS Reserved...". This paragraph talks about how to set the
parameters in the RESPONSE message for case 2. It is basically fine, but the
second sentence is for me not understandable (" For those QSPEC parameters
that were also included in the QoS Available object in the RESERVE message,
their value is copied into the QoS Desired object.")
The paragraph is talking about responses, but in RESPONSE there is no QoS
desired object anymore (at least according to the table above). I probably
do misunderstand something here?
- section 6.1 qspec header element definition. The length definition in the
qspec header definition contradicts the length definition at the beginning
of section 6.1 One says "total length of qspec" the other "length is always
exept header"
- section 6.2.2., see also my comment above about tmod-2. Even after reading
section 6.2.2. I do not have any clue why there two tmod parameters.
- section 6.2.7. The slack term is 32 bits as integer. However the slack
term must only be non-negative, i.e., it is actually an unsigned int. Why is
is not specified as unsigned int? However, the current value range
definition is broken, as an integer of 32 bits cannot have a maximum range
to  2**32-1 (there are only 31 bits left...). This also holds true for other
occasions where integer values are used (e.g. section 6.2.3!
- section 6.2.11. para starting with " When excess treatment is set to
'shape', ". What is the error handling if excess treatment is set to 'shape'
and no TMOD parameter is given?
- section 7. This section is extremely short. This might a non-issue, but I
personally had the feeling the security discussion is too brief. This might
be OK, but the document authors and the WG should be prepared for tough
questions regarding this when going to the IESG. What about this document
defining just the basics, but other documents defining the real behaviour?
Is it assumed that this does not raise any new security issue?
- section 8 says in several places " A specification is required to
depreciate, delete, or modify QSPEC versions." What happens to deleted IANA
values? Is IANA allowed to re-assign those or should they be treated as
deprecated values, i.e., they cannot be used anymore, but the value is
blocked for ever?

****
idnits 2.06.01 

tmp/draft-ietf-nsis-qspec-18.txt:
tmp/draft-ietf-nsis-qspec-18.txt(2867): Found possible IPv4 address
'7.2.9.4' in position 6; this doesn't match RFC3330's suggested 192.0.2.0/24
address range.

  Checking boilerplate required by RFC 3978 and 3979, updated by RFC 4748:
  
----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt:
  
----------------------------------------------------------------------------

  == No 'Intended status' indicated for this document; assuming Proposed
     Standard

  == The page length should not exceed 58 lines per page, but there was 3
     longer pages, the longest (page 6) being 59 lines

  == It seems as if not all pages are separated by form feeds - found 0 form
     feeds but 55 pages


  Checking nits according to http://www.ietf.org/ID-Checklist.html:
  
----------------------------------------------------------------------------

  == There are 1 instance of lines with non-RFC3330-compliant IPv4 addresses
     in the document.  If these are example addresses, they should be
changed.


  Miscellaneous warnings:
  
----------------------------------------------------------------------------

  == The copyright year in the IETF Trust Copyright Line does not match the
     current year


  Checking references for intended status: Proposed Standard
  
----------------------------------------------------------------------------

     (See RFC 3967 for information about using normative references to
     lower-maturity documents in RFCs)

  == Missing Reference: 'S' is mentioned on line 1730, but not defined
     '|  Slack Term [S]  (32-bit integer)                             |...'

  -- Possible downref: Undefined Non-RFC (?) reference : ref. 'S'

  == Unused Reference: 'RFC4506' is defined on line 2363, but no explicit
     reference was found in the text
     '[RFC4506] Eisler, M., "XDR: External Data Representation
Standard,"...'

  == Unused Reference: 'IEEE754' is defined on line 2375, but no explicit
     reference was found in the text
     '[IEEE754] Institute of Electrical and Electronics Engineers, "IEEE
S...'

  == Unused Reference: 'NETWORK-BYTE-ORDER' is defined on line 2381, but no
     explicit reference was found in the text
     '[NETWORK-BYTE-ORDER] Wikipedia, "Endianness,"
http://en.wikipedia.or...'

  -- Possible downref: Non-RFC (?) normative reference: ref. '3GPP-1'

  -- Possible downref: Non-RFC (?) normative reference: ref. '3GPP-2'

  -- Possible downref: Non-RFC (?) normative reference: ref. '3GPP-3'

  -- Possible downref: Non-RFC (?) normative reference: ref. 'GIST'

  -- Possible downref: Non-RFC (?) normative reference: ref. 'QoS-SIG'


     Summary: 0 errors (**), 9 warnings (==), 6 comments (--).
----------------------------------------------------------------------------
----


stiemerling@netlab.nec.de

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
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis



From nsis-bounces@ietf.org Wed Jan 30 09:30:12 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JKDx0-0000jC-1m; Wed, 30 Jan 2008 09:30:06 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JKDww-0000PZ-Nv
	for nsis-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 09:30:02 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JKDww-0000NV-A4; Wed, 30 Jan 2008 09:30:02 -0500
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1JKDwv-0007la-Tr; Wed, 30 Jan 2008 09:30:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id C9BE72AC77;
	Wed, 30 Jan 2008 14:30:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1JKDwv-0007bn-Is; Wed, 30 Jan 2008 09:30:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1JKDwv-0007bn-Is@stiedprstage1.ietf.org>
Date: Wed, 30 Jan 2008 09:30:01 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: nsis@ietf.org
Subject: [NSIS] I-D Action:draft-ietf-nsis-nslp-natfw-17.txt 
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Steps in Signaling Working Group of the IETF.


	Title           : NAT/Firewall NSIS Signaling Layer Protocol (NSLP)
	Author(s)       : M. Stiemerling, et al.
	Filename        : draft-ietf-nsis-nslp-natfw-17.txt
	Pages           : 89
	Date            : 2008-01-30

This memo defines the NSIS Signaling Layer Protocol (NSLP) for
Network Address Translators (NATs) and firewalls.  This NSLP allows
hosts to signal on the data path for NATs and firewalls to be
configured according to the needs of the application data flows.  For
instance, it enables hosts behind NATs to obtain a public reachable
address and hosts behind firewalls to receive data traffic.  The
overall architecture is given by the framework and requirements
defined by the Next Steps in Signaling (NSIS) working group.  The
network scenarios, the protocol itself, and examples for path-coupled
signaling are given in this memo.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nsis-nslp-natfw-17.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-nsis-nslp-natfw-17.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nsis-nslp-natfw-17.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2008-01-30092155.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-nsis-nslp-natfw-17.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-nsis-nslp-natfw-17.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-01-30092155.I-D\@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--





From nsis-bounces@ietf.org Wed Jan 30 09:39:49 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JKE6P-0006Pt-GB; Wed, 30 Jan 2008 09:39:49 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JKE6O-0006Pk-GP
	for nsis-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 09:39:48 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JKE6O-0006Pc-4A
	for nsis@ietf.org; Wed, 30 Jan 2008 09:39:48 -0500
Received: from smtp0.neclab.eu ([195.37.70.41])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JKE6M-00088I-O1
	for nsis@ietf.org; Wed, 30 Jan 2008 09:39:48 -0500
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 310602C002B4A
	for <nsis@ietf.org>; Wed, 30 Jan 2008 15:39:46 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1])
	by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id C+JgU7DeEsQ4 for <nsis@ietf.org>;
	Wed, 30 Jan 2008 15:39:46 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 0BCA22C000355
	for <nsis@ietf.org>; Wed, 30 Jan 2008 15:39:41 +0100 (CET)
Received: from 10.1.1.109 ([10.1.1.109]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Wed, 30 Jan 2008 14:39:40 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Wed, 30 Jan 2008 15:39:34 +0100
Subject: FW: [NSIS] I-D Action:draft-ietf-nsis-nslp-natfw-17.txt 
From: Martin Stiemerling <Stiemerling@nw.neclab.eu>
To: nsis <nsis@ietf.org>
Message-ID: <C3C64ABB.EA6B%Stiemerling@nw.neclab.eu>
Thread-Topic: [NSIS] I-D Action:draft-ietf-nsis-nslp-natfw-17.txt 
Thread-Index: AchjTKxdqmOPjwfzSoqN9aOFZmt28wAAUHXg
In-Reply-To: <E1JKDwv-0007bn-Is@stiedprstage1.ietf.org>
Mime-version: 1.0
Content-type: multipart/mixed;
	boundary="B_3284552379_1046078"
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 3be09dac38eaa50f02d21c7fcee1128c
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3284552379_1046078
Content-type: multipart/alternative;
	boundary="B_3284552379_1075963"


--B_3284552379_1075963
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hi,

This new version of the NATFW NSLP incorporates the comments received in the
WGLC.

Please check if all comments have been addressed properly.

Thanks,

  Martin

Change log natfw-nslp 16 to 17
- Removed section 8 "open issues"
- Removed short form of EXT in favour of calling it always EXTERNAL
- Restructered section 3.2 "Basic Protocol Overview" for better readability
- Added second proxy example in 3.2. (3.2.3.  Signaling for Proxy Mode)
- Fixed different issues of editorial nature
- Clarified on DTINFO; PC-MRM and LE-MRM usage
- Handled Jukka's comments (e-mail Dec 04 2007)
- Handled Niklas' comments (e-mail Dec 11 2007)
- Handled Lauri's comments (e-amil Dec 13 2007)
- Handled Teemu's comments (e-mail Dec 19 2007)
- Changed 'transit' timer definition to 30 seconds, at least.
- Changed Lifetime error messages, i.e., added two new error codes.
- Changed proxy flag error handling for NOTIFY.
- Corrected some misspellings.
- Fixed duplicated stuff in "NSLP Header" section (Hannes' e-mail Jan 30)

   Martin


------ Weitergeleitete Nachricht
Von: <Internet-Drafts@ietf.org>
Datum: Wed, 30 Jan 2008 15:30:01 +0100
An: <i-d-announce@ietf.org>
Cc: <nsis@ietf.org>
Unterhaltung: [NSIS] I-D Action:draft-ietf-nsis-nslp-natfw-17.txt
Betreff: [NSIS] I-D Action:draft-ietf-nsis-nslp-natfw-17.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Next Steps in Signaling Working Group of
the IETF.


        Title           : NAT/Firewall NSIS Signaling Layer Protocol (NSLP)
        Author(s)       : M. Stiemerling, et al.
        Filename        : draft-ietf-nsis-nslp-natfw-17.txt
        Pages           : 89
        Date            : 2008-01-30

This memo defines the NSIS Signaling Layer Protocol (NSLP) for
Network Address Translators (NATs) and firewalls.  This NSLP allows
hosts to signal on the data path for NATs and firewalls to be
configured according to the needs of the application data flows.  For
instance, it enables hosts behind NATs to obtain a public reachable
address and hosts behind firewalls to receive data traffic.  The
overall architecture is given by the framework and requirements
defined by the Next Steps in Signaling (NSIS) working group.  The
network scenarios, the protocol itself, and examples for path-coupled
signaling are given in this memo.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nsis-nslp-natfw-17.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
        "get draft-ietf-nsis-nslp-natfw-17.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-ietf-nsis-nslp-natfw-17.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


------ Ende der weitergeleiteten Nachricht


--B_3284552379_1075963
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>FW: [NSIS] I-D Action:draft-ietf-nsis-nslp-natfw-17.txt </TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'>Hi,<B=
R>
<BR>
This new version of the NATFW NSLP incorporates the comments received in th=
e WGLC.<BR>
<BR>
Please check if all comments have been addressed properly.<BR>
<BR>
Thanks,<BR>
<BR>
&nbsp;&nbsp;Martin<BR>
<BR>
Change log natfw-nslp 16 to 17<BR>
- Removed section 8 &quot;open issues&quot;<BR>
- Removed short form of EXT in favour of calling it always EXTERNAL<BR>
- Restructered section 3.2 &quot;Basic Protocol Overview&quot; for better r=
eadability<BR>
- Added second proxy example in 3.2. (3.2.3. &nbsp;Signaling for Proxy Mode=
)<BR>
- Fixed different issues of editorial nature<BR>
- Clarified on DTINFO; PC-MRM and LE-MRM usage<BR>
- Handled Jukka's comments (e-mail Dec 04 2007)<BR>
- Handled Niklas' comments (e-mail Dec 11 2007)<BR>
- Handled Lauri's comments (e-amil Dec 13 2007)<BR>
- Handled Teemu's comments (e-mail Dec 19 2007)<BR>
- Changed 'transit' timer definition to 30 seconds, at least.<BR>
- Changed Lifetime error messages, i.e., added two new error codes.<BR>
- Changed proxy flag error handling for NOTIFY.<BR>
- Corrected some misspellings.<BR>
- Fixed duplicated stuff in &quot;NSLP Header&quot; section (Hannes' e-mail=
 Jan 30)<BR>
<BR>
&nbsp;&nbsp;&nbsp;Martin<BR>
<BR>
<BR>
------ Weitergeleitete Nachricht<BR>
<B>Von: </B>&lt;Internet-Drafts@ietf.org&gt;<BR>
<B>Datum: </B>Wed, 30 Jan 2008 15:30:01 +0100<BR>
<B>An: </B>&lt;i-d-announce@ietf.org&gt;<BR>
<B>Cc: </B>&lt;nsis@ietf.org&gt;<BR>
<B>Unterhaltung: </B>[NSIS] I-D Action:draft-ietf-nsis-nslp-natfw-17.txt <B=
R>
<B>Betreff: </B>[NSIS] I-D Action:draft-ietf-nsis-nslp-natfw-17.txt <BR>
<BR>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<BR>
This draft is a work item of the Next Steps in Signaling Working Group of t=
he IETF.<BR>
<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title &nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: NAT/Firewall NSIS Signaling Layer P=
rotocol (NSLP)<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Author(s) &nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;: M. Stiemerling, et al.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Filename &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;: draft-ietf-nsis-nslp-natfw-17.txt<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Pages &nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 89<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Date &nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2008-01-30<BR>
<BR>
This memo defines the NSIS Signaling Layer Protocol (NSLP) for<BR>
Network Address Translators (NATs) and firewalls. &nbsp;This NSLP allows<BR=
>
hosts to signal on the data path for NATs and firewalls to be<BR>
configured according to the needs of the application data flows. &nbsp;For<=
BR>
instance, it enables hosts behind NATs to obtain a public reachable<BR>
address and hosts behind firewalls to receive data traffic. &nbsp;The<BR>
overall architecture is given by the framework and requirements<BR>
defined by the Next Steps in Signaling (NSIS) working group. &nbsp;The<BR>
network scenarios, the protocol itself, and examples for path-coupled<BR>
signaling are given in this memo.<BR>
<BR>
A URL for this Internet-Draft is:<BR>
<a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-nsis-nslp-natfw-17.=
txt">http://www.ietf.org/internet-drafts/draft-ietf-nsis-nslp-natfw-17.txt</=
a><BR>
<BR>
To remove yourself from the I-D Announcement list, send a message to<BR>
i-d-announce-request@ietf.org with the word unsubscribe in the body of<BR>
the message.<BR>
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce<BR>
to change your subscription settings.<BR>
<BR>
Internet-Drafts are also available by anonymous FTP. Login with the<BR>
username &quot;anonymous&quot; and a password of your e-mail address. After=
<BR>
logging in, type &quot;cd internet-drafts&quot; and then<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;get draft-ietf-nsis-n=
slp-natfw-17.txt&quot;.<BR>
<BR>
A list of Internet-Drafts directories can be found in<BR>
<a href=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</=
a><BR>
or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/i=
etf/1shadow-sites.txt</a><BR>
<BR>
Internet-Drafts can also be obtained by e-mail.<BR>
<BR>
Send a message to:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;mailserv@ietf.org.<BR>
In the body type:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;FILE /internet-drafts=
/draft-ietf-nsis-nslp-natfw-17.txt&quot;.<BR>
<BR>
NOTE: &nbsp;&nbsp;The mail server at ietf.org can return the document in<BR=
>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;MIME-encoded form by using =
the &quot;mpack&quot; utility. &nbsp;To use this<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;feature, insert the command=
 &quot;ENCODING mime&quot; before the &quot;FILE&quot;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;command. &nbsp;To decode th=
e response(s), you will need &quot;munpack&quot; or<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;a MIME-compliant mail reade=
r. &nbsp;Different MIME-compliant mail readers<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;exhibit different behavior,=
 especially when dealing with<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;multipart&quot; MIME =
messages (i.e. documents which have been split<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;up into multiple messages),=
 so check your local documentation on<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;how to manipulate these mes=
sages.<BR>
<BR>
Below is the data which will enable a MIME compliant mail reader<BR>
implementation to automatically retrieve the ASCII version of the<BR>
Internet-Draft.<BR>
<BR>
<BR>
------ Ende der weitergeleiteten Nachricht<BR>
</SPAN></FONT>
</BODY>
</HTML>


--B_3284552379_1075963--


--B_3284552379_1046078
Content-type: application/octet-stream; name="ATT04004.TXT"
Content-disposition: attachment;
	filename="ATT04004.TXT"
Content-transfer-encoding: base64

Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7IGFjY2Vzcy10eXBlPSJtYWls
LXNlcnZlciI7DQoJc2VydmVyPSJtYWlsc2VydkBpZXRmLm9yZyINCg0KQ29udGVudC1UeXBl
OiB0ZXh0L3BsYWluDQpDb250ZW50LUlEOiA8MjAwOC0wMS0zMDA5MjE1NS5JLURAaWV0Zi5v
cmc+DQoNCkVOQ09ESU5HIG1pbWUNCkZJTEUgL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRm
LW5zaXMtbnNscC1uYXRmdy0xNy50eHQNCg==

--B_3284552379_1046078
Content-type: application/octet-stream;
	name="draft-ietf-nsis-nslp-natfw-17.URL"
Content-disposition: attachment; filename="draft-ietf-nsis-nslp-natfw-17.URL"
Content-transfer-encoding: base64

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRy
YWZ0cy9kcmFmdC1pZXRmLW5zaXMtbnNscC1uYXRmdy0xNy50eHQNCg==

--B_3284552379_1046078
Content-type: application/octet-stream; name="ATT04005.txt"
Content-disposition: attachment;
	filename="ATT04005.txt"
Content-transfer-encoding: base64

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm5zaXMg
bWFpbGluZyBsaXN0DQpuc2lzQGlldGYub3JnDQpodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9uc2lzDQo=

--B_3284552379_1046078
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--B_3284552379_1046078--






From nsis-bounces@ietf.org Wed Jan 30 10:34:42 2008
Return-path: <nsis-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JKExW-0005O9-3O; Wed, 30 Jan 2008 10:34:42 -0500
Received: from nsis by megatron.ietf.org with local (Exim 4.43)
	id 1JKExV-0005O4-8J
	for nsis-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 10:34:41 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JKExU-0005Nv-Tz
	for nsis@ietf.org; Wed, 30 Jan 2008 10:34:40 -0500
Received: from smtp0.neclab.eu ([195.37.70.41])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JKExU-0003dw-Je
	for nsis@ietf.org; Wed, 30 Jan 2008 10:34:40 -0500
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 292632C002B48
	for <nsis@ietf.org>; Wed, 30 Jan 2008 16:34:40 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1])
	by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Fy6CQPUHo9Uy for <nsis@ietf.org>;
	Wed, 30 Jan 2008 16:34:40 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 1515B2C000355
	for <nsis@ietf.org>; Wed, 30 Jan 2008 16:34:35 +0100 (CET)
Received: from 10.1.1.109 ([10.1.1.109]) by mx1.office ([10.1.1.23]) with
	Microsoft Exchange Server HTTP-DAV ; Wed, 30 Jan 2008 15:34:34 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Wed, 30 Jan 2008 16:34:32 +0100
From: Martin Stiemerling <Stiemerling@nw.neclab.eu>
To: nsis <nsis@ietf.org>
Message-ID: <C3C65798.EA7B%Stiemerling@nw.neclab.eu>
Thread-Topic: Supplemental web page about NSIS implementations
Thread-Index: AchjVZv12tBVXc9IEdybRgAWy5Ti1Q==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Subject: [NSIS] Supplemental web page about NSIS implementations
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org

Dear all,

There is now a supplemental web page summarizing the available NSIS
implementations:

ietf.stiemerling.org/

It is not complete yet but will be filled in the next hours.

  Martin



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



