[ippm] OWAMP draft - draft*ietf-ippm-owdp-14.txt

"sharee mcnab" <sharee.mcnab@alliedtelesyn.co.nz> Mon, 24 October 2005 21:38 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUA1G-0002sA-Uh; Mon, 24 Oct 2005 17:38:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUA1F-0002s5-JG for ippm@megatron.ietf.org; Mon, 24 Oct 2005 17:38:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22553 for <ippm@ietf.org>; Mon, 24 Oct 2005 17:38:00 -0400 (EDT)
Received: from gate.alliedtelesyn.co.nz ([202.49.72.33] ident=proxyuser) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EUAE3-0000nP-Ed for ippm@ietf.org; Mon, 24 Oct 2005 17:51:29 -0400
Received: (qmail 18602 invoked from network); 24 Oct 2005 21:37:51 -0000
Received: from mailmarshall.alliedtelesyn.co.nz (10.32.18.40) by gate-int.alliedtelesyn.co.nz with SMTP; 24 Oct 2005 21:37:51 -0000
Received: from aslan.alliedtelesyn.co.nz (Not Verified[10.32.18.53]) by mailmarshall.alliedtelesyn.co.nz with NetIQ MailMarshal (v5.5.6.7) id <B0004462a4>; Tue, 25 Oct 2005 10:37:19 +1300
Received: from CHCDOM1-MTA by aslan.alliedtelesyn.co.nz with Novell_GroupWise; Tue, 25 Oct 2005 10:37:51 +1300
Message-Id: <s35e0aff.047@aslan.alliedtelesyn.co.nz>
X-Mailer: Novell GroupWise Internet Agent 6.5.4
Date: Tue, 25 Oct 2005 10:37:14 +1300
From: sharee mcnab <sharee.mcnab@alliedtelesyn.co.nz>
To: ippm@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Spam-Score: 0.2 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: quoted-printable
Cc:
Subject: [ippm] OWAMP draft - draft*ietf-ippm-owdp-14.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org >
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org ?subject=unsubscribe>
List-Post: <mailto:ippm@ietf.org >
List-Help: <mailto:ippm-request@ietf.org ?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org ?subject=subscribe>
Sender: ippm-bounces@ietf.org
Errors-To: ippm-bounces@ietf.org

Hello,
At ATR, we've been looking into OWAMP (as well as TWAMP) and had the following questions.  Perhaps the authors or others could answer these questions?

A.  Page 5.  Section 2, paragraph 2.  States OWAMP-control messages use a "Well-known port number" (ie 0-1023).  Is it planned to designate & register a defined OWAMP port number for OWAMP-control messages?

B.  Page 14. Section 3.5 Generally Server-> Sender/Receiver interactions for setting up tests and retrieving test data are undefined for the more general architecture where the various modules are on separate hosts.  This obviously impacts interoperability in the more general architecture.  Is it be worth extending the standard to include these interactions or alternatively defining the standard to limited architectures, maybe with an extension for the more general case?

C.  Section 3.5, second to last paragraph.  Setting the Conf-Sender and Conf-Receiver seems inconsequential when it is the Control-Client speaking to the Server.  Surely this is only of importance when the Server is speaking to the Sender/Receiver.  Also, what is to stop the sender & receiver checking the sender/ receiver address field to determine if they are the receiver or sender?

D.  The OWAMP draft has a strong emphasis on security and encryption.  It is not clear to me though that there are enough implementation details in the draft to enable interoperability with regards to security keys?  Is this the intention or is it planned to have limited interoperability in authenticated and encrypted modes?


Thanks again

Sharee McNab
Nick Kinraid

NOTICE: This message contains privileged and confidential
information intended only for the use of the addressee
named above. If you are not the intended recipient of
this message you are hereby notified that you must not
disseminate, copy or take any action in reliance on it.
If you have received this message in error please
notify Allied Telesyn Research Ltd immediately.
Any views expressed in this message are those of the
individual sender, except where the sender has the
authority to issue and specifically states them to
be the views of Allied Telesyn Research.

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