From owner-ietf-sacred@mail.imc.org  Fri Feb  1 07:06:52 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19533
	for <sacred-archive@odin.ietf.org>; Fri, 1 Feb 2002 07:06:51 -0500 (EST)
Received: by above.proper.com (8.11.6/8.11.3) id g11C1gD25805
	for ietf-sacred-bks; Fri, 1 Feb 2002 04:01:42 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g11C1e325798
	for <ietf-sacred@imc.org>; Fri, 1 Feb 2002 04:01:40 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19403;
	Fri, 1 Feb 2002 07:01:37 -0500 (EST)
Message-Id: <200202011201.HAA19403@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-sacred@imc.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sacred-protocol-bss-01.txt
Date: Fri, 01 Feb 2002 07:01:37 -0500
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Securely Available Credentials Working Group of the IETF.

	Title		: Securely Available Credentials Protocol
	Author(s)	: S. Farrell
	Filename	: draft-ietf-sacred-protocol-bss-01.txt
	Pages		: 20
	Date		: 31-Jan-02
	
This document describes an SRP-based protocol for securely available
credentials.
Discussion of this draft is taking place on the SACRED mailing list
of the IETF SACRED working group (see http://www.imc.org/ietf-sacred
for subscription information).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sacred-protocol-bss-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-sacred-protocol-bss-01.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-sacred-protocol-bss-01.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:	<20020131131435.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sacred-protocol-bss-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sacred-protocol-bss-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--




From owner-ietf-sacred@mail.imc.org  Fri Feb  1 11:53:43 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03135
	for <sacred-archive@odin.ietf.org>; Fri, 1 Feb 2002 11:53:42 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g11Gmpv09888
	for ietf-sacred-bks; Fri, 1 Feb 2002 08:48:51 -0800 (PST)
Received: from ocasey.baltimore.com (ocasey.baltimore.com [193.41.17.101])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g11Gmn309883
	for <ietf-sacred@imc.org>; Fri, 1 Feb 2002 08:48:49 -0800 (PST)
Received: from Baltimore-FW1 ([172.19.1.1])
	by ocasey.baltimore.com (8.11.6/8.9.3) with SMTP id g11GmoU07652
	for <ietf-sacred@imc.org>; Fri, 1 Feb 2002 16:48:50 GMT
Received: from Baltimore-FW1 (wilde-i-1.ie.baltimore.com) by emeairlsw1.baltimore.com
 (Content Technologies SMTPRS 4.2.5) with SMTP id <T58cefdb4dd0a99193517b@emeairlsw1.baltimore.com> for <ietf-sacred@imc.org>;
 Fri, 1 Feb 2002 16:44:15 +0000
Received: from baltimore.ie (wks140-4.ie.baltimore.com [10.153.4.140])
	by bobcat.baltimore.ie (8.9.3/8.9.3) with ESMTP id QAA22457
	for <ietf-sacred@imc.org>; Fri, 1 Feb 2002 16:48:47 GMT
Message-ID: <3C5AC733.1F590B92@baltimore.ie>
Date: Fri, 01 Feb 2002 16:49:55 +0000
From: Stephen Farrell <stephen.farrell@baltimore.ie>
Reply-To: stephen.farrell@baltimore.ie
Organization: Baltimore Technologies Ltd.
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-sacred@imc.org
Subject: Re: I-D ACTION:draft-ietf-sacred-protocol-bss-01.txt
References: <200202011201.HAA19403@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit



Hi All,

Just to give you the context for this draft. 

I've tried to fix all of the issues that we had resolved on 
the mailing list and to indicate those where we haven't 
reached concensus (yet:-). 

Since I had to trawl the archives and there were some issues 
raised where I didn't see a clear resolution, there're probably 
a few things I missed. If you're commenting on this, can you try 
to make sure that we tackle these each in a separate thread so I
can pick 'em up more easily next time round?

I'll then do up another version prior to the cutoff date for 
Minneapolis reflecting the status at that point (towards the 
end of the month).

At that stage we should be in good shape to try to finalize even
the major issues we've left (though its interesting that everyone
ran out of steam over the holiday:-),

Regards,
Stephen.

Internet-Drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Securely Available Credentials Working Group of the IETF.
> 
>         Title           : Securely Available Credentials Protocol
>         Author(s)       : S. Farrell
>         Filename        : draft-ietf-sacred-protocol-bss-01.txt
>         Pages           : 20
>         Date            : 31-Jan-02
> 
> This document describes an SRP-based protocol for securely available
> credentials.
> Discussion of this draft is taking place on the SACRED mailing list
> of the IETF SACRED working group (see http://www.imc.org/ietf-sacred
> for subscription information).
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sacred-protocol-bss-01.txt
> 
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the message.
> 
> 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-sacred-protocol-bss-01.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-sacred-protocol-bss-01.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:     <20020131131435.I-D@ietf.org>

-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 881 6716
39 Parkgate Street,                     fax: +353 1 881 7000
Dublin 8.                mailto:stephen.farrell@baltimore.ie
Ireland                             http://www.baltimore.com


From owner-ietf-sacred@mail.imc.org  Tue Feb  5 03:00:52 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25035
	for <sacred-archive@lists.ietf.org>; Tue, 5 Feb 2002 03:00:52 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g157pmX10754
	for ietf-sacred-bks; Mon, 4 Feb 2002 23:51:48 -0800 (PST)
Received: from tholian.rsasecurity.com (mail.rsasecurity.com [204.167.112.129])
	by above.proper.com (8.11.6/8.11.3) with SMTP id g157pk310745
	for <ietf-sacred@imc.org>; Mon, 4 Feb 2002 23:51:46 -0800 (PST)
Received: from sdtihq24.securitydynamics.com by tholian.rsasecurity.com
          via smtpd (for mail.imc.org [208.184.76.43]) with SMTP; 5 Feb 2002 07:51:11 UT
Received: from ebola.securitydynamics.com (ebola.securid.com [192.168.7.4])
	by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id CAA27470
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 02:51:45 -0500 (EST)
Received: from spirit.dynas.se (localhost [127.0.0.1])
	by ebola.securitydynamics.com (8.10.2+Sun/8.9.1) with SMTP id g157pgk28765
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 02:51:42 -0500 (EST)
Received: (qmail 10830 invoked from network); 5 Feb 2002 07:51:41 -0000
Received: from dsf.dynas.se (192.168.102.2)
  by spirit.dynas.se with SMTP; 5 Feb 2002 07:51:41 -0000
Received: (qmail 55021 invoked from network); 5 Feb 2002 07:51:40 -0000
Received: from karoni.sto.dynas.se (HELO mnystrom-lap) (192.168.102.2)
  by karoni.sto.dynas.se with SMTP; 5 Feb 2002 07:51:40 -0000
Date: Tue, 5 Feb 2002 08:51:42 +0100 (W. Europe Standard Time)
From: Magnus Nystrom <magnus@rsasecurity.com>
To: ietf-sacred@imc.org
cc: Stephen Farrell <stephen.farrell@baltimore.ie>
Subject: BEEP adjustments [was: Re: I-D ACTION:draft-ietf-sacred-protocol-bss-01.txt]
Message-ID: <Pine.WNT.4.43.0202050849090.1500-100000@mnystrom-lap>
X-X-Sender: magnus@dsf.dynas.se
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>


(No, _this_ message is _not_ about the substrate issue ;)

Stephen,

Thanks for your work in producing this draft.

In order to clarify the separation between the messages themselves and the
BEEP profile more clearly, I suggest that the places where BEEP is
mentioned before the current Section 4 are rewritten slightly.

Specifically, the changes I would like to see are

Section 1:

s/The protocol uses [BEEP]/The protocol is profiled for BEEP [BEEP]/

Section 2.3:

(See separate posting regarding SRP, but in case that is not well
received, at least:

s/sTLS means that the BEEP session MUST be "tuned" for
server-authenticated TLS/sTLS means server-authenticated TLS/

s/cTLS means that the BEEP session MUST be "tuned" for
mutually-authenticated TLS/cTLS means client-authenticated TLS/

s/SRP means that the BEEP session MUST be "tuned" for SASL-SRP;/SRP means
SASL-SRP;/

and then move the para about "tuned" BEEP sessions to the BEEP profile
section.

Section 2.4:

Drop 2.4 since it does not make things more secure or efficient but adds
confusion (e.g. is there some operational requirement that requires the
server to drop the connection after a successful exchange?)

Section 3.1:

Replace the last two paragraphs with:

   "Where no specific response message is defined for an operation (e.g.
   for UploadRequest) then the transport will indicate success or
   failure.

   All of the response messages defined here MAY contain a Status
   string, containing a value intended for human consumption."

(The BEEP profile already specifies the mapping to BEEP messages)

BR,
-- Magnus



From owner-ietf-sacred@mail.imc.org  Tue Feb  5 03:55:21 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25046
	for <sacred-archive@lists.ietf.org>; Tue, 5 Feb 2002 03:00:54 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g157qiV11000
	for ietf-sacred-bks; Mon, 4 Feb 2002 23:52:44 -0800 (PST)
Received: from tholian.rsasecurity.com (mail.rsasecurity.com [204.167.112.129])
	by above.proper.com (8.11.6/8.11.3) with SMTP id g157qh310991
	for <ietf-sacred@imc.org>; Mon, 4 Feb 2002 23:52:43 -0800 (PST)
Received: from sdtihq24.securitydynamics.com by tholian.rsasecurity.com
          via smtpd (for mail.imc.org [208.184.76.43]) with SMTP; 5 Feb 2002 07:52:07 UT
Received: from ebola.securitydynamics.com (ebola.securid.com [192.168.7.4])
	by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id CAA27514
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 02:52:42 -0500 (EST)
Received: from spirit.dynas.se (localhost [127.0.0.1])
	by ebola.securitydynamics.com (8.10.2+Sun/8.9.1) with SMTP id g157qeQ28822
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 02:52:40 -0500 (EST)
Received: (qmail 10855 invoked from network); 5 Feb 2002 07:52:39 -0000
Received: from dsf.dynas.se (192.168.102.2)
  by spirit.dynas.se with SMTP; 5 Feb 2002 07:52:39 -0000
Received: (qmail 55046 invoked from network); 5 Feb 2002 07:52:38 -0000
Received: from karoni.sto.dynas.se (HELO mnystrom-lap) (192.168.102.2)
  by karoni.sto.dynas.se with SMTP; 5 Feb 2002 07:52:38 -0000
Date: Tue, 5 Feb 2002 08:52:39 +0100 (W. Europe Standard Time)
From: Magnus Nystrom <magnus@rsasecurity.com>
To: ietf-sacred@imc.org
cc: Stephen Farrell <stephen.farrell@baltimore.ie>
Subject: SRP adjustments [was: Re: I-D ACTION:draft-ietf-sacred-protocol-bss-01.txt]
Message-ID: <Pine.WNT.4.43.0202050847290.1500-100000@mnystrom-lap>
X-X-Sender: magnus@dsf.dynas.se
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>


Stephen,

In the posting I made on Dec 6th, there was a suggestion to modify the
protocol document to allow for other security context establishment
mechanisms apart from SRP. While it is necessary to mandate one
authentication mechanism for interoperability reasons, I do not think
that it should be left completely unspecified how to implement support
for other mechanisms, in particular since the current draft is based
on BEEP which supports SASL which in turn supports many mechanisms.

Specifically, the changes that I would like to see are:

-Section 1, second para:

Delete first sentence, since, e.g., cTLS is also allowed. Rephrase the
paragraph to:

	The protocol uses [BEEP] for its exchange model

(or possibly: "The protocol is profiled for BEEP...", see separate
 thread "BEEP adjustments")

        and its	payloads consist of a set of XML messages defined
	herein. The protocol sets out to meet the requirements in
	[REQS]. In particular, security requirements in [REQS] are met
	by mandating support for TLS [TLS] and/or SRP [SRP].

-Section 2.1.2:

Change second para to:

   The purpose of this operation is to setup a new account on the
   server.  The information required for a "new" account
   will depend on the SASL mechanism used.  For [SRP], it will consist
   of the username and SRP password verifier with no associated
   credentials.

-Section 2.1.4:

Remove the current subsection, and replace it with:

   2.1.4 Modify Account

   The purpose of this operation is to allow the client to change the
   information required for authentication.  The information required
   will depend on the authentication method used. For [SRP] it will
   consist of a salt and a password verifier value.  Once the account
   information has been changed, the server will respond an error or
   acknowledgement message."

-Section 2.3:

(The reasons for the changes proposed for this section are as follows:
The security requirements are not really cTLS, sTLS or SASL-SRP, but
rather the security services these protocols provide. It therefore
seems more correct to identify these required services, and then
identify protocols that provides them, and finally mandate a minimum
set -that must be supported in order to guarantee interoperability-
among those protocols)

Delete the last sentence in the first paragraph, and delete the
listing after it. From this follows that the Note also will be
deleted. Replace the remaining text with:

      Operation                 Security REQUIRED
      ---------                 -----------------
      Information request       NONE
      Create account            Server authentication,
				Privacy, Integrity
      Remove account            Mutual authentication,
				Privacy, Integrity
      Modify account            Mutual authentication,
				Privacy, Integrity
      Credential upload         Mutual authentication,
`				Privacy, Integrity
      Credential download       Mutual authentication,
				Privacy, Integrity

   The security requirements can be met by several mechanisms. This
   document REQUIRES credential servers to support TLS and SASL-SRP.
   Clients MUST support SASL-SRP or TLS.

   The mandatory-to-implement TLS cipher suite for SACRED is
   TLS_RSA_WITH_3DES-EDE_CBC_SHA.

   For SASL-SRP, all three security services (privacy,
   replay protection, and integrity) MUST be used.

[The issue of the authorization identity have to be dealt with in a
separate thread]

-Section 3:

Change "PWChangeRequest" to "ModifyAccountRequest" throughout the
section.

-Section 3.5:

Replace current text with:

   Contains one or more element containing the information
   required to create an account for the identified authentication
   mechanism.  The actual information contained in the element will be
   defined by the authentication mechanism but for SRP it will contain
   the account name, salt and password verifier for that account.

-Section 3.7:

Replace current text with:

   Contains one or more element containing new authentication
   information for identified authentication mechanisms.  The actual
   information contained in the elements will depend on the mechanism
   but for SRP it will contains a new salt and password verifier for
   the account.

-Appendix A:

If the above proposal is accepted, it means that the schema must be
updated to allow for other SASL mechanisms and changed PDU names. In
the message I sent to the list on Dec. 6 there was a proposal on how
to achieve this (separate from the http/BEEP issue), although that
proposal was flexible enough to handle also non-SASL mechanisms. It is
probably ok to limit ourselves to SASL (and TLS) mechanisms for now,
but my suggestion is to make use of the parts of that proposal that
are needed for the above. Of course I (and Gareth) are willing to help
out in formulating that schema.

BR,
-- Magnus





From owner-ietf-sacred@mail.imc.org  Tue Feb  5 07:15:25 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27990
	for <sacred-archive@lists.ietf.org>; Tue, 5 Feb 2002 07:15:24 -0500 (EST)
Received: by above.proper.com (8.11.6/8.11.3) id g15C8IQ11311
	for ietf-sacred-bks; Tue, 5 Feb 2002 04:08:18 -0800 (PST)
Received: from tholian.rsasecurity.com (mail.rsasecurity.com [204.167.112.129])
	by above.proper.com (8.11.6/8.11.3) with SMTP id g15C8H311307
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 04:08:17 -0800 (PST)
Received: from sdtihq24.securid.com by tholian.rsasecurity.com
          via smtpd (for mail.imc.org [208.184.76.43]) with SMTP; 5 Feb 2002 12:07:43 UT
Received: from ebola.securitydynamics.com (ebola.securid.com [192.168.7.4])
	by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id HAA08349
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 07:08:17 -0500 (EST)
Received: from spirit.dynas.se (localhost [127.0.0.1])
	by ebola.securitydynamics.com (8.10.2+Sun/8.9.1) with SMTP id g15C8FE11470
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 07:08:15 -0500 (EST)
Received: (qmail 22403 invoked from network); 5 Feb 2002 12:08:14 -0000
Received: from grichards-lap2.d.dynas.se (HELO grichardslap2) (172.16.13.203)
  by spirit.dynas.se with SMTP; 5 Feb 2002 12:08:14 -0000
From: "Gareth Richards" <grichards@rsasecurity.com>
To: <ietf-sacred@imc.org>
Cc: "Stephen Farrell" <stephen.farrell@baltimore.ie>
Subject: MultipleCredentials [was: Re: I-D ACTION:draft-ietf-sacred-protocol-bss-01.txt]
Date: Tue, 5 Feb 2002 12:08:08 -0000
Message-ID: <IMEPKJJBLAOOOLIELKEJEEKBCAAA.grichards@rsasecurity.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit


Stephen,

Here are some comments on the modified support for multiple credentials in
draft-ietf-sacred-protocol-bss-01.txt,

1. In the schema, <CredentialSelector> is optional in sacred:CredentialType
but since all credentials MUST have a selector (section 2.5) it does not
seem as if it is valid for this element to not be present.

I therefore suggest that

         <element name="CredentialSelector" type="string" minOccurs="0"/>

be replaced with

         <element name="CredentialSelector" type="string" />


2. Since it is possible for a user to request all their credentials, a
DownloadResponse needs to be able to contain more than one credential.
(Section 2.5 states that "If the selector is omitted in a download request
it MUST be interpreted as a request for all the stored credentials.")

Section 3.9 should say something like

   This message contains the credentials.

And in the schema, the <DownloadResponse> element needs to be able to
contain more than one <Credential> element.  One possibility would be

     <element name="DownloadResponse">
       <complexType>
         <sequence>
           <element name="Status" type="string" minOccurs="0"/>
           <element name="Credential" type="sacred:CredentialType"
maxOccurs="unbounded"/>
         </sequence>
       </complexType>
     </element>

3. In the schema, the credential selector is called CredSel in a
<DownloadRequest> and CredentialSelector in the <sacred:CredentialType>

I think that since these are both referring to the same thing they should
have the same name.




From owner-ietf-sacred@mail.imc.org  Tue Feb  5 07:30:29 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28352
	for <sacred-archive@lists.ietf.org>; Tue, 5 Feb 2002 07:30:29 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g15CJ6G11969
	for ietf-sacred-bks; Tue, 5 Feb 2002 04:19:06 -0800 (PST)
Received: from tholian.rsasecurity.com (mail.rsasecurity.com [204.167.112.129])
	by above.proper.com (8.11.6/8.11.3) with SMTP id g15CJ5311965
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 04:19:05 -0800 (PST)
Received: from sdtihq24.securitydynamics.com by tholian.rsasecurity.com
          via smtpd (for mail.imc.org [208.184.76.43]) with SMTP; 5 Feb 2002 12:18:30 UT
Received: from ebola.securitydynamics.com (ebola.securid.com [192.168.7.4])
	by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id HAA08791
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 07:19:05 -0500 (EST)
Received: from spirit.dynas.se (localhost [127.0.0.1])
	by ebola.securitydynamics.com (8.10.2+Sun/8.9.1) with SMTP id g15CJ3g11994
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 07:19:03 -0500 (EST)
Received: (qmail 22924 invoked from network); 5 Feb 2002 12:19:02 -0000
Received: from grichards-lap2.d.dynas.se (HELO grichardslap2) (172.16.13.203)
  by spirit.dynas.se with SMTP; 5 Feb 2002 12:19:02 -0000
From: "Gareth Richards" <grichards@rsasecurity.com>
To: <ietf-sacred@imc.org>
Cc: "Stephen Farrell" <stephen.farrell@baltimore.ie>
Subject: Protocol Versioning [was: Re: I-D ACTION:draft-ietf-sacred-protocol-bss-01.txt]
Date: Tue, 5 Feb 2002 12:18:56 -0000
Message-ID: <IMEPKJJBLAOOOLIELKEJMEKBCAAA.grichards@rsasecurity.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit


Stephen,

None of the PDUs described in the current ID contain version information.
I suggest that this may be needed to support future version of SACRED.

I was also wondering if it might be worth placing these attributes and any
other information common to all message types in abstract base types
similar to the RequestAbstractType and ResultAbstract type of XKMS as this
may make the schema simpler.

For example,

  <complexType name="RequestAbstractType" abstract="true">
    <sequence>
      <element ref="sacred:ProcessInfo" minOccurs="0"/>
    </sequence>
    <attribute name="MajorVersion" type="nonNegativeInteger" use="required"
fixed="1"/>
    <attribute name="MinorVersion" type="nonNegativeInteger" use="required"
fixed="0"/>
  </complexType>

   <complexType name="ResponseAbstractType" abstract="true">
    <sequence>
       <element name="Status" type="string" minOccurs="0"/>
    </sequence>
    <attribute name="MajorVersion" type="nonNegativeInteger" use="required"
fixed="1"/>
    <attribute name="MinorVersion" type="nonNegativeInteger" use="required"
fixed="0"/>
  </complexType>


There are a couple of other issues related to schema.

I noticed that you added XML complexity as a major open issue.  Could you
expand on this.

Do we really need to maintain a DTD and a schema? Since it is possible to
generate a DTD from a schema then wouldn't a schema be sufficient? It seems
as is not just unnecessary but also potentially harmful due to possible
discrepancies.



From owner-ietf-sacred@mail.imc.org  Tue Feb  5 07:33:06 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28423
	for <sacred-archive@lists.ietf.org>; Tue, 5 Feb 2002 07:33:05 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g15CQg612786
	for ietf-sacred-bks; Tue, 5 Feb 2002 04:26:42 -0800 (PST)
Received: from ocasey.baltimore.com (ocasey.baltimore.com [193.41.17.101])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g15CQe312782
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 04:26:40 -0800 (PST)
Received: from Baltimore-FW1 ([172.19.1.1])
	by ocasey.baltimore.com (8.11.6/8.9.3) with SMTP id g15CQeU17935
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 12:26:40 GMT
Received: from Baltimore-FW1 (wilde-i-1.ie.baltimore.com) by emeairlsw1.baltimore.com
 (Content Technologies SMTPRS 4.2.5) with SMTP id <T58e2a714710a99193517b@emeairlsw1.baltimore.com> for <ietf-sacred@imc.org>;
 Tue, 5 Feb 2002 12:22:02 +0000
Received: from baltimore.ie (wks140-4.ie.baltimore.com [10.153.4.140])
	by bobcat.baltimore.ie (8.9.3/8.9.3) with ESMTP id MAA14735;
	Tue, 5 Feb 2002 12:26:38 GMT
Message-ID: <3C5FCFC5.731D6EF0@baltimore.ie>
Date: Tue, 05 Feb 2002 12:27:49 +0000
From: Stephen Farrell <stephen.farrell@baltimore.ie>
Reply-To: stephen.farrell@baltimore.ie
Organization: Baltimore Technologies Ltd.
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Magnus Nystrom <magnus@rsasecurity.com>
CC: ietf-sacred@imc.org
Subject: Re: BEEP adjustments [was: Re: I-D 
 ACTION:draft-ietf-sacred-protocol-bss-01.txt]
References: <Pine.WNT.4.43.0202050849090.1500-100000@mnystrom-lap>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit



All ok for me, except about 2.4 (see below).

Stephen.

Magnus Nystrom wrote:
> 
> (No, _this_ message is _not_ about the substrate issue ;)
> 
> Stephen,
> 
> Thanks for your work in producing this draft.
> 
> In order to clarify the separation between the messages themselves and the
> BEEP profile more clearly, I suggest that the places where BEEP is
> mentioned before the current Section 4 are rewritten slightly.
> 
> Specifically, the changes I would like to see are
> 
> Section 1:
> 
> s/The protocol uses [BEEP]/The protocol is profiled for BEEP [BEEP]/
> 
> Section 2.3:
> 
> (See separate posting regarding SRP, but in case that is not well
> received, at least:
> 
> s/sTLS means that the BEEP session MUST be "tuned" for
> server-authenticated TLS/sTLS means server-authenticated TLS/
> 
> s/cTLS means that the BEEP session MUST be "tuned" for
> mutually-authenticated TLS/cTLS means client-authenticated TLS/
> 
> s/SRP means that the BEEP session MUST be "tuned" for SASL-SRP;/SRP means
> SASL-SRP;/
> 
> and then move the para about "tuned" BEEP sessions to the BEEP profile
> section.
> 
> Section 2.4:
> 
> Drop 2.4 since it does not make things more secure or efficient but adds
> confusion (e.g. is there some operational requirement that requires the
> server to drop the connection after a successful exchange?)

Don't we need to say somewhere whether the session is expected to be
kept open? I don't see any requirement that a sacred server keep the
connection open, and I think its simpler if it just handles a single
transaction per connection/session. Hence the current text. I wouldn't
agree that saying nothing is right though.

> Section 3.1:
> 
> Replace the last two paragraphs with:
> 
>    "Where no specific response message is defined for an operation (e.g.
>    for UploadRequest) then the transport will indicate success or
>    failure.
> 
>    All of the response messages defined here MAY contain a Status
>    string, containing a value intended for human consumption."
> 
> (The BEEP profile already specifies the mapping to BEEP messages)
> 
> BR,
> -- Magnus

-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 881 6716
39 Parkgate Street,                     fax: +353 1 881 7000
Dublin 8.                mailto:stephen.farrell@baltimore.ie
Ireland                             http://www.baltimore.com


From owner-ietf-sacred@mail.imc.org  Tue Feb  5 07:35:05 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28452
	for <sacred-archive@lists.ietf.org>; Tue, 5 Feb 2002 07:35:04 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g15CN0c12308
	for ietf-sacred-bks; Tue, 5 Feb 2002 04:23:00 -0800 (PST)
Received: from ocasey.baltimore.com (ocasey.baltimore.com [193.41.17.101])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g15CMv312301
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 04:22:58 -0800 (PST)
Received: from Baltimore-FW1 ([172.19.1.1])
	by ocasey.baltimore.com (8.11.6/8.9.3) with SMTP id g15CMwU17889
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 12:22:58 GMT
Received: from Baltimore-FW1 (wilde-i-1.ie.baltimore.com) by emeairlsw1.baltimore.com
 (Content Technologies SMTPRS 4.2.5) with SMTP id <T58e2a3afda0a99193517b@emeairlsw1.baltimore.com> for <ietf-sacred@imc.org>;
 Tue, 5 Feb 2002 12:18:20 +0000
Received: from baltimore.ie (wks140-4.ie.baltimore.com [10.153.4.140])
	by bobcat.baltimore.ie (8.9.3/8.9.3) with ESMTP id MAA14684;
	Tue, 5 Feb 2002 12:22:54 GMT
Message-ID: <3C5FCEE6.82AC14EC@baltimore.ie>
Date: Tue, 05 Feb 2002 12:24:06 +0000
From: Stephen Farrell <stephen.farrell@baltimore.ie>
Reply-To: stephen.farrell@baltimore.ie
Organization: Baltimore Technologies Ltd.
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Gareth Richards <grichards@rsasecurity.com>
CC: ietf-sacred@imc.org
Subject: Re: MultipleCredentials [was: Re: I-D 
 ACTION:draft-ietf-sacred-protocol-bss-01.txt]
References: <IMEPKJJBLAOOOLIELKEJEEKBCAAA.grichards@rsasecurity.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit



Gareth,

This looks fine to me. I'll include it in the next rev
if there're no objections.

Stephen.

Gareth Richards wrote:
> 
> Stephen,
> 
> Here are some comments on the modified support for multiple credentials in
> draft-ietf-sacred-protocol-bss-01.txt,
> 
> 1. In the schema, <CredentialSelector> is optional in sacred:CredentialType
> but since all credentials MUST have a selector (section 2.5) it does not
> seem as if it is valid for this element to not be present.
> 
> I therefore suggest that
> 
>          <element name="CredentialSelector" type="string" minOccurs="0"/>
> 
> be replaced with
> 
>          <element name="CredentialSelector" type="string" />
> 
> 2. Since it is possible for a user to request all their credentials, a
> DownloadResponse needs to be able to contain more than one credential.
> (Section 2.5 states that "If the selector is omitted in a download request
> it MUST be interpreted as a request for all the stored credentials.")
> 
> Section 3.9 should say something like
> 
>    This message contains the credentials.
> 
> And in the schema, the <DownloadResponse> element needs to be able to
> contain more than one <Credential> element.  One possibility would be
> 
>      <element name="DownloadResponse">
>        <complexType>
>          <sequence>
>            <element name="Status" type="string" minOccurs="0"/>
>            <element name="Credential" type="sacred:CredentialType"
> maxOccurs="unbounded"/>
>          </sequence>
>        </complexType>
>      </element>
> 
> 3. In the schema, the credential selector is called CredSel in a
> <DownloadRequest> and CredentialSelector in the <sacred:CredentialType>
> 
> I think that since these are both referring to the same thing they should
> have the same name.

-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 881 6716
39 Parkgate Street,                     fax: +353 1 881 7000
Dublin 8.                mailto:stephen.farrell@baltimore.ie
Ireland                             http://www.baltimore.com


From owner-ietf-sacred@mail.imc.org  Tue Feb  5 07:43:49 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28583
	for <sacred-archive@lists.ietf.org>; Tue, 5 Feb 2002 07:43:49 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g15CVUC12900
	for ietf-sacred-bks; Tue, 5 Feb 2002 04:31:30 -0800 (PST)
Received: from ocasey.baltimore.com (ocasey.baltimore.com [193.41.17.101])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g15CVS312892
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 04:31:28 -0800 (PST)
Received: from Baltimore-FW1 ([172.19.1.1])
	by ocasey.baltimore.com (8.11.6/8.9.3) with SMTP id g15CVSU17997
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 12:31:28 GMT
Received: from Baltimore-FW1 (wilde-i-1.ie.baltimore.com) by emeairlsw1.baltimore.com
 (Content Technologies SMTPRS 4.2.5) with SMTP id <T58e2ab7b170a99193517b@emeairlsw1.baltimore.com> for <ietf-sacred@imc.org>;
 Tue, 5 Feb 2002 12:26:51 +0000
Received: from baltimore.ie (wks140-4.ie.baltimore.com [10.153.4.140])
	by bobcat.baltimore.ie (8.9.3/8.9.3) with ESMTP id MAA14808;
	Tue, 5 Feb 2002 12:31:24 GMT
Message-ID: <3C5FD0E4.95A5354A@baltimore.ie>
Date: Tue, 05 Feb 2002 12:32:36 +0000
From: Stephen Farrell <stephen.farrell@baltimore.ie>
Reply-To: stephen.farrell@baltimore.ie
Organization: Baltimore Technologies Ltd.
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Gareth Richards <grichards@rsasecurity.com>
CC: ietf-sacred@imc.org
Subject: Re: Protocol Versioning [was: Re: I-D 
 ACTION:draft-ietf-sacred-protocol-bss-01.txt]
References: <IMEPKJJBLAOOOLIELKEJMEKBCAAA.grichards@rsasecurity.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit



Gareth,

'Fraid I at least don't like these suggested changes!

For versioning - there's already a namespace & beep profile, what 
more's needed?

I'd also rather not start using abtract types in the schema since
I don't see much saving and in any case, I noted an open issue in
the draft (whether DTD or schema should be normative) that should
be closed before we try using (what I think is) fancy schema stuff.

Finally, I note that the DTD automatically generated from schema that
my tool produces is total garbarge and drags in all sorts of dsig
stuff, has a lot of repetition etc. So no, I don't think a schema
is sufficient is there's a set of folks who prefer DTDs. Another
reason for us to first decide which (DTD/schema) to make normative.

Stephen.

Gareth Richards wrote:
> 
> Stephen,
> 
> None of the PDUs described in the current ID contain version information.
> I suggest that this may be needed to support future version of SACRED.
> 
> I was also wondering if it might be worth placing these attributes and any
> other information common to all message types in abstract base types
> similar to the RequestAbstractType and ResultAbstract type of XKMS as this
> may make the schema simpler.
> 
> For example,
> 
>   <complexType name="RequestAbstractType" abstract="true">
>     <sequence>
>       <element ref="sacred:ProcessInfo" minOccurs="0"/>
>     </sequence>
>     <attribute name="MajorVersion" type="nonNegativeInteger" use="required"
> fixed="1"/>
>     <attribute name="MinorVersion" type="nonNegativeInteger" use="required"
> fixed="0"/>
>   </complexType>
> 
>    <complexType name="ResponseAbstractType" abstract="true">
>     <sequence>
>        <element name="Status" type="string" minOccurs="0"/>
>     </sequence>
>     <attribute name="MajorVersion" type="nonNegativeInteger" use="required"
> fixed="1"/>
>     <attribute name="MinorVersion" type="nonNegativeInteger" use="required"
> fixed="0"/>
>   </complexType>
> 
> There are a couple of other issues related to schema.
> 
> I noticed that you added XML complexity as a major open issue.  Could you
> expand on this.
> 
> Do we really need to maintain a DTD and a schema? Since it is possible to
> generate a DTD from a schema then wouldn't a schema be sufficient? It seems
> as is not just unnecessary but also potentially harmful due to possible
> discrepancies.

-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 881 6716
39 Parkgate Street,                     fax: +353 1 881 7000
Dublin 8.                mailto:stephen.farrell@baltimore.ie
Ireland                             http://www.baltimore.com


From owner-ietf-sacred@mail.imc.org  Tue Feb  5 07:48:11 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28664
	for <sacred-archive@lists.ietf.org>; Tue, 5 Feb 2002 07:48:10 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g15Caxf13250
	for ietf-sacred-bks; Tue, 5 Feb 2002 04:36:59 -0800 (PST)
Received: from ocasey.baltimore.com (ocasey.baltimore.com [193.41.17.101])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g15Cav313243
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 04:36:57 -0800 (PST)
Received: from Baltimore-FW1 ([172.19.1.1])
	by ocasey.baltimore.com (8.11.6/8.9.3) with SMTP id g15CavU18098
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 12:36:57 GMT
Received: from Baltimore-FW1 (wilde-i-1.ie.baltimore.com) by emeairlsw1.baltimore.com
 (Content Technologies SMTPRS 4.2.5) with SMTP id <T58e2b07ed70a99193517b@emeairlsw1.baltimore.com> for <ietf-sacred@imc.org>;
 Tue, 5 Feb 2002 12:32:19 +0000
Received: from baltimore.ie (wks140-4.ie.baltimore.com [10.153.4.140])
	by bobcat.baltimore.ie (8.9.3/8.9.3) with ESMTP id MAA14928;
	Tue, 5 Feb 2002 12:36:54 GMT
Message-ID: <3C5FD22E.26D6D021@baltimore.ie>
Date: Tue, 05 Feb 2002 12:38:06 +0000
From: Stephen Farrell <stephen.farrell@baltimore.ie>
Reply-To: stephen.farrell@baltimore.ie
Organization: Baltimore Technologies Ltd.
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Magnus Nystrom <magnus@rsasecurity.com>
CC: ietf-sacred@imc.org
Subject: Re: SRP adjustments [was: Re: I-D 
 ACTION:draft-ietf-sacred-protocol-bss-01.txt]
References: <Pine.WNT.4.43.0202050847290.1500-100000@mnystrom-lap>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit



Magnus,

This all looks fine to me, though I might change some wording when
I'm editing, so barring objections I'll add these in for the next
rev.

Stephen.

Magnus Nystrom wrote:
> 
> Stephen,
> 
> In the posting I made on Dec 6th, there was a suggestion to modify the
> protocol document to allow for other security context establishment
> mechanisms apart from SRP. While it is necessary to mandate one
> authentication mechanism for interoperability reasons, I do not think
> that it should be left completely unspecified how to implement support
> for other mechanisms, in particular since the current draft is based
> on BEEP which supports SASL which in turn supports many mechanisms.
> 
> Specifically, the changes that I would like to see are:
> 
> -Section 1, second para:
> 
> Delete first sentence, since, e.g., cTLS is also allowed. Rephrase the
> paragraph to:
> 
>         The protocol uses [BEEP] for its exchange model
> 
> (or possibly: "The protocol is profiled for BEEP...", see separate
>  thread "BEEP adjustments")
> 
>         and its payloads consist of a set of XML messages defined
>         herein. The protocol sets out to meet the requirements in
>         [REQS]. In particular, security requirements in [REQS] are met
>         by mandating support for TLS [TLS] and/or SRP [SRP].
> 
> -Section 2.1.2:
> 
> Change second para to:
> 
>    The purpose of this operation is to setup a new account on the
>    server.  The information required for a "new" account
>    will depend on the SASL mechanism used.  For [SRP], it will consist
>    of the username and SRP password verifier with no associated
>    credentials.
> 
> -Section 2.1.4:
> 
> Remove the current subsection, and replace it with:
> 
>    2.1.4 Modify Account
> 
>    The purpose of this operation is to allow the client to change the
>    information required for authentication.  The information required
>    will depend on the authentication method used. For [SRP] it will
>    consist of a salt and a password verifier value.  Once the account
>    information has been changed, the server will respond an error or
>    acknowledgement message."
> 
> -Section 2.3:
> 
> (The reasons for the changes proposed for this section are as follows:
> The security requirements are not really cTLS, sTLS or SASL-SRP, but
> rather the security services these protocols provide. It therefore
> seems more correct to identify these required services, and then
> identify protocols that provides them, and finally mandate a minimum
> set -that must be supported in order to guarantee interoperability-
> among those protocols)
>
> Delete the last sentence in the first paragraph, and delete the
> listing after it. From this follows that the Note also will be
> deleted. Replace the remaining text with:
> 
>       Operation                 Security REQUIRED
>       ---------                 -----------------
>       Information request       NONE
>       Create account            Server authentication,
>                                 Privacy, Integrity
>       Remove account            Mutual authentication,
>                                 Privacy, Integrity
>       Modify account            Mutual authentication,
>                                 Privacy, Integrity
>       Credential upload         Mutual authentication,
> `                               Privacy, Integrity
>       Credential download       Mutual authentication,
>                                 Privacy, Integrity
> 
>    The security requirements can be met by several mechanisms. This
>    document REQUIRES credential servers to support TLS and SASL-SRP.
>    Clients MUST support SASL-SRP or TLS.
> 
>    The mandatory-to-implement TLS cipher suite for SACRED is
>    TLS_RSA_WITH_3DES-EDE_CBC_SHA.
> 
>    For SASL-SRP, all three security services (privacy,
>    replay protection, and integrity) MUST be used.
> 
> [The issue of the authorization identity have to be dealt with in a
> separate thread]
> 
> -Section 3:
> 
> Change "PWChangeRequest" to "ModifyAccountRequest" throughout the
> section.
> 
> -Section 3.5:
> 
> Replace current text with:
> 
>    Contains one or more element containing the information
>    required to create an account for the identified authentication
>    mechanism.  The actual information contained in the element will be
>    defined by the authentication mechanism but for SRP it will contain
>    the account name, salt and password verifier for that account.
> 
> -Section 3.7:
> 
> Replace current text with:
> 
>    Contains one or more element containing new authentication
>    information for identified authentication mechanisms.  The actual
>    information contained in the elements will depend on the mechanism
>    but for SRP it will contains a new salt and password verifier for
>    the account.
> 
> -Appendix A:
> 
> If the above proposal is accepted, it means that the schema must be
> updated to allow for other SASL mechanisms and changed PDU names. In
> the message I sent to the list on Dec. 6 there was a proposal on how
> to achieve this (separate from the http/BEEP issue), although that
> proposal was flexible enough to handle also non-SASL mechanisms. It is
> probably ok to limit ourselves to SASL (and TLS) mechanisms for now,
> but my suggestion is to make use of the parts of that proposal that
> are needed for the above. Of course I (and Gareth) are willing to help
> out in formulating that schema.
> 
> BR,
> -- Magnus

-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 881 6716
39 Parkgate Street,                     fax: +353 1 881 7000
Dublin 8.                mailto:stephen.farrell@baltimore.ie
Ireland                             http://www.baltimore.com


From owner-ietf-sacred@mail.imc.org  Tue Feb  5 07:53:08 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28732
	for <sacred-archive@lists.ietf.org>; Tue, 5 Feb 2002 07:53:08 -0500 (EST)
Received: by above.proper.com (8.11.6/8.11.3) id g15Ckdf13589
	for ietf-sacred-bks; Tue, 5 Feb 2002 04:46:39 -0800 (PST)
Received: from ocasey.baltimore.com (ocasey.baltimore.com [193.41.17.101])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g15Ckb313585
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 04:46:38 -0800 (PST)
Received: from Baltimore-FW1 ([172.19.1.1])
	by ocasey.baltimore.com (8.11.6/8.9.3) with SMTP id g15CkcU18229
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 12:46:38 GMT
Received: from Baltimore-FW1 (wilde-i-1.ie.baltimore.com) by emeairlsw1.baltimore.com
 (Content Technologies SMTPRS 4.2.5) with SMTP id <T58e2b95a8b0a99193517b@emeairlsw1.baltimore.com> for <ietf-sacred@imc.org>;
 Tue, 5 Feb 2002 12:42:00 +0000
Received: from baltimore.ie (wks140-4.ie.baltimore.com [10.153.4.140])
	by bobcat.baltimore.ie (8.9.3/8.9.3) with ESMTP id MAA15156
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 12:46:35 GMT
Message-ID: <3C5FD473.4F981E96@baltimore.ie>
Date: Tue, 05 Feb 2002 12:47:47 +0000
From: Stephen Farrell <stephen.farrell@baltimore.ie>
Reply-To: stephen.farrell@baltimore.ie
Organization: Baltimore Technologies Ltd.
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-sacred <ietf-sacred@imc.org>
Subject: "unbounded"
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit



I just noticed that one of the changes Gareth wanted is to 
allow >1 credential in a download response (which is fine,
given the new way we're using the cred selector string).

His suggested schema includes:

>   <element name="Credential" type="sacred:CredentialType"
>      maxOccurs="unbounded"/>

Now, my (set of related) questions are: 

- How should we handle "unbounded" in general? ("not using
  it" is my favorite answer:-)
- How many credentials/account MUST a credential server be 
  able to handle? (Is anything other than "[0|1|many]" really 
  plausible? How about "at least 10/acount"?)
- MUST a client be able to handle the same number or would
  a client that can only handle one credential be ok? (Any
  other subtleties there?)
- Are there any DoS or buffer-overrun attacks possible, that
  are related to this usage? (or some other "unbounded" - this 
  case seems ok since the message is inherently from an 
  authenticated source, at least with beep).

Maybe there're other things too?

Stephen.


-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 881 6716
39 Parkgate Street,                     fax: +353 1 881 7000
Dublin 8.                mailto:stephen.farrell@baltimore.ie
Ireland                             http://www.baltimore.com


From owner-ietf-sacred@mail.imc.org  Tue Feb  5 09:28:53 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00826
	for <sacred-archive@lists.ietf.org>; Tue, 5 Feb 2002 09:28:52 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g15EN9D20428
	for ietf-sacred-bks; Tue, 5 Feb 2002 06:23:09 -0800 (PST)
Received: from tholian.rsasecurity.com (mail.rsasecurity.com [204.167.112.129])
	by above.proper.com (8.11.6/8.11.3) with SMTP id g15EN8320422
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 06:23:08 -0800 (PST)
Received: from sdtihq24.securid.com by tholian.rsasecurity.com
          via smtpd (for mail.imc.org [208.184.76.43]) with SMTP; 5 Feb 2002 14:22:34 UT
Received: from ebola.securitydynamics.com (ebola.securid.com [192.168.7.4])
	by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id JAA18183
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 09:23:09 -0500 (EST)
Received: from spirit.dynas.se (localhost [127.0.0.1])
	by ebola.securitydynamics.com (8.10.2+Sun/8.9.1) with SMTP id g15EN2O22627
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 09:23:02 -0500 (EST)
Received: (qmail 28761 invoked from network); 5 Feb 2002 14:23:01 -0000
Received: from grichards-lap2.d.dynas.se (HELO grichardslap2) (172.16.13.203)
  by spirit.dynas.se with SMTP; 5 Feb 2002 14:23:01 -0000
From: "Gareth Richards" <grichards@rsasecurity.com>
To: <ietf-sacred@imc.org>
Cc: "Stephen Farrell" <stephen.farrell@baltimore.ie>
Subject: LastModified [was: Re: I-D ACTION:draft-ietf-sacred-protocol-bss-01.txt]
Date: Tue, 5 Feb 2002 14:22:54 -0000
Message-ID: <IMEPKJJBLAOOOLIELKEJIEKCCAAA.grichards@rsasecurity.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit


Stephen,

Section 3.10 of draft-ietf-sacred-protocol-bss-01.txt describes the use of
the LastModified and PrevLastModified values in UploadRequest.

I am concerned that there may be a potential for problems if we rely on the
clients to set this time when they may have inaccurate clocks.  It does not
appear as if there is a problem in detecting conflicts during upload since
the actual value of LastModified is not important (the server can treat it
as an opaque blob) but there may be potential problems on the client.

If a user did the following

Download to platform A, update from A, download to platform B

then there could be some confusion if the clock on platform A was ahead of
that on platform B.  The user could be told that "your credentials were
last modified tomorrow".

The same section states

   Note: A server SHOULD ensure that the LastModified value in the new
   credential is reasonably accurate. If it isn't then the server
   SHOULD respond with an error message in which case, the server MUST
   NOT store the new credential.

This seems to imply that it will only be possible for clients with clocks
in close agreement with the server to upload credentials.  It therefore
seems as if it would be safer to have a LastUploaded time maintained by the
server.

I therefore suggest that PrevLastModified be removed.

Section 3.2

Second item be replaced with

   - LastModified specifies the time at which this credential was last
     changed on the server.

Section 3.10

Remove first two paragraphs and replace PrevLastModifed with LastModifed in
second two.



From owner-ietf-sacred@mail.imc.org  Tue Feb  5 09:47:18 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01445
	for <sacred-archive@lists.ietf.org>; Tue, 5 Feb 2002 09:47:17 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g15Eg0W21989
	for ietf-sacred-bks; Tue, 5 Feb 2002 06:42:00 -0800 (PST)
Received: from ocasey.baltimore.com (ocasey.baltimore.com [193.41.17.101])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g15Efw321975
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 06:41:58 -0800 (PST)
Received: from Baltimore-FW1 ([172.19.1.1])
	by ocasey.baltimore.com (8.11.6/8.9.3) with SMTP id g15EfwU19743
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 14:41:58 GMT
Received: from Baltimore-FW1 (wilde-i-1.ie.baltimore.com) by emeairlsw1.baltimore.com
 (Content Technologies SMTPRS 4.2.5) with SMTP id <T58e322f3ee0a99193517b@emeairlsw1.baltimore.com> for <ietf-sacred@imc.org>;
 Tue, 5 Feb 2002 14:37:20 +0000
Received: from baltimore.ie (wks140-4.ie.baltimore.com [10.153.4.140])
	by bobcat.baltimore.ie (8.9.3/8.9.3) with ESMTP id OAA17043;
	Tue, 5 Feb 2002 14:41:54 GMT
Message-ID: <3C5FEF7A.DBC2926@baltimore.ie>
Date: Tue, 05 Feb 2002 14:43:06 +0000
From: Stephen Farrell <stephen.farrell@baltimore.ie>
Reply-To: stephen.farrell@baltimore.ie
Organization: Baltimore Technologies Ltd.
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Gareth Richards <grichards@rsasecurity.com>
CC: ietf-sacred@imc.org
Subject: Re: LastModified [was: Re: I-D 
 ACTION:draft-ietf-sacred-protocol-bss-01.txt]
References: <IMEPKJJBLAOOOLIELKEJIEKCCAAA.grichards@rsasecurity.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit



Gareth,

Not sure which way we should go on this one (anyone else?). Agree
that not depending on a client clock is good though.

If we do take this approach then I'd probably want to take the 
LastModified from the inner sequence of credential structure just 
in case someone sometime wants to e.g. sign our credential 
structure (the problem of course would  be that the server 
would be modifying, making xml signing harder to do).

Shouldn't be a problem to do that, just means having separate 
"inner" & "outer" structures maybe (partly including an earlier 
change) like:

    <complexType name="CredentialsType">
      <sequence>
        <element name="LatestLastModified" type="dateTime"/>
        <element name="Creds" type="sacred:OuterCredentialType"
           maxOccurs="10" /> <!-- I *may* only be kidding about this:-) -->
      </sequence>
    </complexType>
	
    <complexType name="OuterCredentialType">
      <sequence>
        <element name="LastModified" type="dateTime"/>
	<element name="Cred" type="sacred:InnerCredentialType" />
      </sequence>
    </complexType>

     <complexType name="InnerCredentialType">
       <sequence>
         <element name="CredentialSelector" type="string" />
         <element name="Payload" type="ds:KeyInfoType"/>
         <element name="TimeToLive" type="string" minOccurs="0"/>
         <element ref="sacred:ProcessInfo" minOccurs="0"/>
         <element ref="sacred:ClientInfo" minOccurs="0"/>
       </sequence>
     </complexType>

Questions:-

- other suggestions?
- any point in both LatestLastModified and LastModified?

Stephen.

Gareth Richards wrote:
> 
> Stephen,
> 
> Section 3.10 of draft-ietf-sacred-protocol-bss-01.txt describes the use of
> the LastModified and PrevLastModified values in UploadRequest.
> 
> I am concerned that there may be a potential for problems if we rely on the
> clients to set this time when they may have inaccurate clocks.  It does not
> appear as if there is a problem in detecting conflicts during upload since
> the actual value of LastModified is not important (the server can treat it
> as an opaque blob) but there may be potential problems on the client.
> 
> If a user did the following
> 
> Download to platform A, update from A, download to platform B
> 
> then there could be some confusion if the clock on platform A was ahead of
> that on platform B.  The user could be told that "your credentials were
> last modified tomorrow".
> 
> The same section states
> 
>    Note: A server SHOULD ensure that the LastModified value in the new
>    credential is reasonably accurate. If it isn't then the server
>    SHOULD respond with an error message in which case, the server MUST
>    NOT store the new credential.
> 
> This seems to imply that it will only be possible for clients with clocks
> in close agreement with the server to upload credentials.  It therefore
> seems as if it would be safer to have a LastUploaded time maintained by the
> server.
> 
> I therefore suggest that PrevLastModified be removed.
> 
> Section 3.2
> 
> Second item be replaced with
> 
>    - LastModified specifies the time at which this credential was last
>      changed on the server.
> 
> Section 3.10
> 
> Remove first two paragraphs and replace PrevLastModifed with LastModifed in
> second two.

-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 881 6716
39 Parkgate Street,                     fax: +353 1 881 7000
Dublin 8.                mailto:stephen.farrell@baltimore.ie
Ireland                             http://www.baltimore.com


From owner-ietf-sacred@mail.imc.org  Tue Feb  5 11:48:39 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07781
	for <sacred-archive@lists.ietf.org>; Tue, 5 Feb 2002 11:48:39 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g15Ggaj28906
	for ietf-sacred-bks; Tue, 5 Feb 2002 08:42:36 -0800 (PST)
Received: from tholian.rsasecurity.com (mail.rsasecurity.com [204.167.112.129])
	by above.proper.com (8.11.6/8.11.3) with SMTP id g15GgZ328898
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 08:42:35 -0800 (PST)
Received: from sdtihq24.securitydynamics.com by tholian.rsasecurity.com
          via smtpd (for mail.imc.org [208.184.76.43]) with SMTP; 5 Feb 2002 16:42:01 UT
Received: from ebola.securitydynamics.com (ebola.securid.com [192.168.7.4])
	by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id LAA02559
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 11:42:36 -0500 (EST)
Received: from spirit.dynas.se (localhost [127.0.0.1])
	by ebola.securitydynamics.com (8.10.2+Sun/8.9.1) with SMTP id g15GgVN09055
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 11:42:31 -0500 (EST)
Received: (qmail 6368 invoked from network); 5 Feb 2002 16:42:30 -0000
Received: from grichards-lap2.d.dynas.se (HELO grichardslap2) (172.16.13.203)
  by spirit.dynas.se with SMTP; 5 Feb 2002 16:42:30 -0000
From: "Gareth Richards" <grichards@rsasecurity.com>
To: <stephen.farrell@baltimore.ie>
Cc: <ietf-sacred@imc.org>
Subject: RE: LastModified [was: Re: I-D  ACTION:draft-ietf-sacred-protocol-bss-01.txt]
Date: Tue, 5 Feb 2002 16:42:23 -0000
Message-ID: <IMEPKJJBLAOOOLIELKEJIEKDCAAA.grichards@rsasecurity.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
In-Reply-To: <3C5FEF7A.DBC2926@baltimore.ie>
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit


Stephen,

I don't really see the need for the LatestLastModified since the client
could easily work it out from the individual LastModified values of the
credentials it downloaded.  Also, if the same CredentialType is used for
uploads, a client would have to set this value itself and we would be back
where we started.

Should we allow multiple credentials to be uploaded in a single
UploadRequest?

How about this variation:

     <complexType name="CredentialType">
       <sequence>
         <element name="LastModified" type="dateTime"/>
         <element name="Cred" type="sacred:InnerCredentialType" />
      </sequence>

     </complexType>

      <complexType name="InnerCredentialType">
        <sequence>
          <element name="CredentialSelector" type="string" />
          <element name="Payload" type="ds:KeyInfoType"/>
          <element name="TimeToLive" type="string" minOccurs="0"/>
          <element ref="sacred:ProcessInfo" minOccurs="0"/>
          <element ref="sacred:ClientInfo" minOccurs="0"/>
        </sequence>
      </complexType>

     <element name="UploadRequest">
       <complexType>
         <sequence>
           <element name="Credential" type="sacred:CredentialType"/>
         </sequence>
       </complexType>
     </element>

     <element name="DownloadResponse">
       <complexType>
         <sequence>
           <element name="Status" type="string" minOccurs="0"/>
           <element name="Credentials" type="sacred:CredentialType"
maxOccurs="unbounded"/>
         </sequence>
       </complexType>
     </element>

> -----Original Message-----
> From: owner-ietf-sacred@mail.imc.org
> [mailto:owner-ietf-sacred@mail.imc.org]On Behalf Of Stephen Farrell
> Sent: 05 February 2002 14:43
> To: Gareth Richards
> Cc: ietf-sacred@imc.org
> Subject: Re: LastModified [was: Re: I-D
> ACTION:draft-ietf-sacred-protocol-bss-01.txt]
>
>
>
>
> Gareth,
>
> Not sure which way we should go on this one (anyone else?). Agree
> that not depending on a client clock is good though.
>
> If we do take this approach then I'd probably want to take the
> LastModified from the inner sequence of credential structure just
> in case someone sometime wants to e.g. sign our credential
> structure (the problem of course would  be that the server
> would be modifying, making xml signing harder to do).
>
> Shouldn't be a problem to do that, just means having separate
> "inner" & "outer" structures maybe (partly including an earlier
> change) like:
>
>     <complexType name="CredentialsType">
>       <sequence>
>         <element name="LatestLastModified" type="dateTime"/>
>         <element name="Creds" type="sacred:OuterCredentialType"
>            maxOccurs="10" /> <!-- I *may* only be kidding about
> this:-) -->
>       </sequence>
>     </complexType>
>
>     <complexType name="OuterCredentialType">
>       <sequence>
>         <element name="LastModified" type="dateTime"/>
> 	<element name="Cred" type="sacred:InnerCredentialType" />
>       </sequence>
>     </complexType>
>
>      <complexType name="InnerCredentialType">
>        <sequence>
>          <element name="CredentialSelector" type="string" />
>          <element name="Payload" type="ds:KeyInfoType"/>
>          <element name="TimeToLive" type="string" minOccurs="0"/>
>          <element ref="sacred:ProcessInfo" minOccurs="0"/>
>          <element ref="sacred:ClientInfo" minOccurs="0"/>
>        </sequence>
>      </complexType>
>
> Questions:-
>
> - other suggestions?
> - any point in both LatestLastModified and LastModified?
>
> Stephen.
>
> Gareth Richards wrote:
> >
> > Stephen,
> >
> > Section 3.10 of draft-ietf-sacred-protocol-bss-01.txt
> describes the use of
> > the LastModified and PrevLastModified values in UploadRequest.
> >
> > I am concerned that there may be a potential for problems if
> we rely on the
> > clients to set this time when they may have inaccurate clocks.
>  It does not
> > appear as if there is a problem in detecting conflicts during
> upload since
> > the actual value of LastModified is not important (the server
> can treat it
> > as an opaque blob) but there may be potential problems on the client.
> >
> > If a user did the following
> >
> > Download to platform A, update from A, download to platform B
> >
> > then there could be some confusion if the clock on platform A
> was ahead of
> > that on platform B.  The user could be told that "your credentials were
> > last modified tomorrow".
> >
> > The same section states
> >
> >    Note: A server SHOULD ensure that the LastModified value in the new
> >    credential is reasonably accurate. If it isn't then the server
> >    SHOULD respond with an error message in which case, the server MUST
> >    NOT store the new credential.
> >
> > This seems to imply that it will only be possible for clients
> with clocks
> > in close agreement with the server to upload credentials.  It therefore
> > seems as if it would be safer to have a LastUploaded time
> maintained by the
> > server.
> >
> > I therefore suggest that PrevLastModified be removed.
> >
> > Section 3.2
> >
> > Second item be replaced with
> >
> >    - LastModified specifies the time at which this credential was last
> >      changed on the server.
> >
> > Section 3.10
> >
> > Remove first two paragraphs and replace PrevLastModifed with
> LastModifed in
> > second two.
>
> --
> ____________________________________________________________
> Stephen Farrell
> Baltimore Technologies,   tel: (direct line) +353 1 881 6716
> 39 Parkgate Street,                     fax: +353 1 881 7000
> Dublin 8.                mailto:stephen.farrell@baltimore.ie
> Ireland                             http://www.baltimore.com
>



From owner-ietf-sacred@mail.imc.org  Tue Feb  5 14:05:58 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14079
	for <sacred-archive@lists.ietf.org>; Tue, 5 Feb 2002 14:05:57 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g15J08k04826
	for ietf-sacred-bks; Tue, 5 Feb 2002 11:00:08 -0800 (PST)
Received: from miz-mishtal.dbc.mtview.ca.us (adsl-64-168-10-250.dsl.scrm01.pacbell.net [64.168.10.250])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g15J07304819
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 11:00:07 -0800 (PST)
Received: from FATORA (dhcpd253 [64.168.10.253] (may be forged))
	by miz-mishtal.dbc.mtview.ca.us (8.11.0+3.3W/8.11.0) with SMTP id g15InsQ07097;
	Tue, 5 Feb 2002 10:49:58 -0800 (PST)
Message-ID: <060c01c1ae77$43ed2200$0301000a@FATORA>
From: "Marshall T. Rose" <mrose@dbc.mtview.ca.us>
To: "Magnus Nystrom" <magnus@rsasecurity.com>, <ietf-sacred@imc.org>
Cc: "Stephen Farrell" <stephen.farrell@baltimore.ie>,
        "Marshall Rose" <mrose@dbc.mtview.ca.us>
References: <Pine.WNT.4.43.0202050849090.1500-100000@mnystrom-lap>
Subject: Re: BEEP adjustments [was: Re: I-D ACTION:draft-ietf-sacred-protocol-bss-01.txt]
Date: Tue, 5 Feb 2002 10:59:35 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit


i think the beep adjustments are fine, as are the srp adjustments.

/mtr




From owner-ietf-sacred@mail.imc.org  Tue Feb  5 14:06:58 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14132
	for <sacred-archive@lists.ietf.org>; Tue, 5 Feb 2002 14:06:57 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g15J1bJ04865
	for ietf-sacred-bks; Tue, 5 Feb 2002 11:01:37 -0800 (PST)
Received: from miz-mishtal.dbc.mtview.ca.us (adsl-64-168-10-250.dsl.scrm01.pacbell.net [64.168.10.250])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g15J1a304861
	for <ietf-sacred@imc.org>; Tue, 5 Feb 2002 11:01:36 -0800 (PST)
Received: from FATORA (dhcpd253 [64.168.10.253] (may be forged))
	by miz-mishtal.dbc.mtview.ca.us (8.11.0+3.3W/8.11.0) with SMTP id g15IpcQ07105;
	Tue, 5 Feb 2002 10:51:38 -0800 (PST)
Message-ID: <060d01c1ae77$7fcee010$0301000a@FATORA>
From: "Marshall T. Rose" <mrose@dbc.mtview.ca.us>
To: <stephen.farrell@baltimore.ie>, "Magnus Nystrom" <magnus@rsasecurity.com>
Cc: <ietf-sacred@imc.org>, "Marshall Rose" <mrose@dbc.mtview.ca.us>
References: <Pine.WNT.4.43.0202050849090.1500-100000@mnystrom-lap> <3C5FCFC5.731D6EF0@baltimore.ie>
Subject: Re: BEEP adjustments [was: Re: I-D  ACTION:draft-ietf-sacred-protocol-bss-01.txt]
Date: Tue, 5 Feb 2002 11:01:20 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit


> > Drop 2.4 since it does not make things more secure or efficient but adds
> > confusion (e.g. is there some operational requirement that requires the
> > server to drop the connection after a successful exchange?)
>
> Don't we need to say somewhere whether the session is expected to be
> kept open? I don't see any requirement that a sacred server keep the
> connection open, and I think its simpler if it just handles a single
> transaction per connection/session. Hence the current text. I wouldn't
> agree that saying nothing is right though.

well, actually, saying nothing is exactly what you want to do.

it's pretty much up to the initiator to decide what they want to do with the
session.

while a listener should certainly have an idle timeout, it's rather
presumptuous on the part of the listener to handle one request and then
exit.

all section 2.4 does is add a fair amount of implementational burden for no
added gain.

/mtr




From owner-ietf-sacred@mail.imc.org  Wed Feb  6 04:59:14 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15455
	for <sacred-archive@odin.ietf.org>; Wed, 6 Feb 2002 04:59:14 -0500 (EST)
Received: by above.proper.com (8.11.6/8.11.3) id g169p3h08235
	for ietf-sacred-bks; Wed, 6 Feb 2002 01:51:03 -0800 (PST)
Received: from ocasey.baltimore.com (ocasey.baltimore.com [193.41.17.101])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g169p1308231
	for <ietf-sacred@imc.org>; Wed, 6 Feb 2002 01:51:01 -0800 (PST)
Received: from Baltimore-FW1 ([172.19.1.1])
	by ocasey.baltimore.com (8.11.6/8.9.3) with SMTP id g169p0U28121
	for <ietf-sacred@imc.org>; Wed, 6 Feb 2002 09:51:00 GMT
Received: from Baltimore-FW1 (wilde-i-1.ie.baltimore.com) by emeairlsw1.baltimore.com
 (Content Technologies SMTPRS 4.2.5) with SMTP id <T58e73ee9810a99193517b@emeairlsw1.baltimore.com> for <ietf-sacred@imc.org>;
 Wed, 6 Feb 2002 09:46:21 +0000
Received: from baltimore.ie (wks140-4.ie.baltimore.com [10.153.4.140])
	by bobcat.baltimore.ie (8.9.3/8.9.3) with ESMTP id JAA29886;
	Wed, 6 Feb 2002 09:50:58 GMT
Message-ID: <3C60FBFA.3C612E6E@baltimore.ie>
Date: Wed, 06 Feb 2002 09:48:42 +0000
From: Stephen Farrell <stephen.farrell@baltimore.ie>
Reply-To: stephen.farrell@baltimore.ie
Organization: Baltimore Technologies Ltd.
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Marshall T. Rose" <mrose@dbc.mtview.ca.us>
CC: Magnus Nystrom <magnus@rsasecurity.com>, ietf-sacred@imc.org
Subject: Re: BEEP adjustments [was: Re: I-D  
 ACTION:draft-ietf-sacred-protocol-bss-01.txt]
References: <Pine.WNT.4.43.0202050849090.1500-100000@mnystrom-lap> <3C5FCFC5.731D6EF0@baltimore.ie> <060d01c1ae77$7fcee010$0301000a@FATORA>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit



> while a listener should certainly have an idle timeout, it's rather
> presumptuous on the part of the listener to handle one request and then
> exit.

For many protocols that's true I guess. However, since we're just 
handling (almost always) credential downloads I'd have thought it 
was just the right behaviour.

However, if you're saying that BEEP makes this a non-issue since
both sides should gracefully terminate (even if one times out),
then I guess I can buy not being so prescriptive. 

So - if no-one wants to keep 2.4 (or similar language), I'll delete 
it, but will add something about avoiding DoS (listener having a 
timeout etc) to the security considerations section. (That text
must nearly be boilerplate by now - anyone know where I can lift
it from?)

Stephen.

-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 881 6716
39 Parkgate Street,                     fax: +353 1 881 7000
Dublin 8.                mailto:stephen.farrell@baltimore.ie
Ireland                             http://www.baltimore.com


From owner-ietf-sacred@mail.imc.org  Wed Feb  6 14:42:58 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29611
	for <sacred-archive@odin.ietf.org>; Wed, 6 Feb 2002 14:42:58 -0500 (EST)
Received: by above.proper.com (8.11.6/8.11.3) id g16JXKh20685
	for ietf-sacred-bks; Wed, 6 Feb 2002 11:33:20 -0800 (PST)
Received: from miz-mishtal.dbc.mtview.ca.us (adsl-64-168-10-250.dsl.scrm01.pacbell.net [64.168.10.250])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g16JXJ320681
	for <ietf-sacred@imc.org>; Wed, 6 Feb 2002 11:33:19 -0800 (PST)
Received: from FATORA (dhcpd253 [64.168.10.253] (may be forged))
	by miz-mishtal.dbc.mtview.ca.us (8.11.0+3.3W/8.11.0) with SMTP id g16JN1Q11088;
	Wed, 6 Feb 2002 11:23:05 -0800 (PST)
Message-ID: <00ea01c1af45$11cbd5e0$0301000a@FATORA>
From: "Marshall T. Rose" <mrose@dbc.mtview.ca.us>
To: <stephen.farrell@baltimore.ie>
Cc: "Magnus Nystrom" <magnus@rsasecurity.com>, <ietf-sacred@imc.org>,
        "Marshall Rose" <mrose@dbc.mtview.ca.us>
References: <Pine.WNT.4.43.0202050849090.1500-100000@mnystrom-lap> <3C5FCFC5.731D6EF0@baltimore.ie> <060d01c1ae77$7fcee010$0301000a@FATORA> <3C60FBFA.3C612E6E@baltimore.ie>
Subject: Re: BEEP adjustments [was: Re: I-D   ACTION:draft-ietf-sacred-protocol-bss-01.txt]
Date: Wed, 6 Feb 2002 11:32:47 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit


> So - if no-one wants to keep 2.4 (or similar language), I'll delete
> it, but will add something about avoiding DoS (listener having a
> timeout etc) to the security considerations section. (That text
> must nearly be boilerplate by now - anyone know where I can lift
> it from?)

in the security section, just add a sentence indicating that, as with all
protocols, a listener implementation should implement an inactivity timer.

/mtr




From owner-ietf-sacred@mail.imc.org  Thu Feb 14 10:12:23 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23851
	for <sacred-archive@odin.ietf.org>; Thu, 14 Feb 2002 10:12:22 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g1EF6U304846
	for ietf-sacred-bks; Thu, 14 Feb 2002 07:06:30 -0800 (PST)
Received: from ocasey.baltimore.com (ocasey.baltimore.com [193.41.17.101])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g1EF6R304841
	for <ietf-sacred@imc.org>; Thu, 14 Feb 2002 07:06:28 -0800 (PST)
Received: from Baltimore-FW1 ([172.19.1.1])
	by ocasey.baltimore.com (8.11.6/8.9.3) with SMTP id g1EF6SU27734
	for <ietf-sacred@imc.org>; Thu, 14 Feb 2002 15:06:28 GMT
Received: from Baltimore-FW1 (wilde-i-1.ie.baltimore.com) by emeairlsw1.baltimore.com
 (Content Technologies SMTPRS 4.2.5) with SMTP id <T59119284e80a99193517b@emeairlsw1.baltimore.com> for <ietf-sacred@imc.org>;
 Thu, 14 Feb 2002 15:01:44 +0000
Received: from baltimore.ie (wks140-4.ie.baltimore.com [10.153.4.140])
	by bobcat.baltimore.ie (8.9.3/8.9.3) with ESMTP id PAA29484
	for <ietf-sacred@imc.org>; Thu, 14 Feb 2002 15:06:26 GMT
Message-ID: <3C6BD1F1.347E75E7@baltimore.ie>
Date: Thu, 14 Feb 2002 15:04:17 +0000
From: Stephen Farrell <stephen.farrell@baltimore.ie>
Reply-To: stephen.farrell@baltimore.ie
Organization: Baltimore Technologies Ltd.
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-sacred <ietf-sacred@imc.org>
Subject: speke draft
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit



Just FYI - a new I-D on speke [1] (with an accompanying 
ipr "declaration" [2]).

Stephen.

[1] http://www.ietf.org/internet-drafts/draft-jablon-speke-00.txt
[2] http://www.ietf.org/ietf/IPR/PHOENIX-SRP-RFC2945.txt

-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 881 6716
39 Parkgate Street,                     fax: +353 1 881 7000
Dublin 8.                mailto:stephen.farrell@baltimore.ie
Ireland                             http://www.baltimore.com


From owner-ietf-sacred@mail.imc.org  Thu Feb 14 11:58:38 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27596
	for <sacred-archive@odin.ietf.org>; Thu, 14 Feb 2002 11:58:35 -0500 (EST)
Received: by above.proper.com (8.11.6/8.11.3) id g1EGrfI10076
	for ietf-sacred-bks; Thu, 14 Feb 2002 08:53:41 -0800 (PST)
Received: from dc-mx07.cluster1.charter.net ([209.225.8.17])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g1EGre310072
	for <ietf-sacred@imc.org>; Thu, 14 Feb 2002 08:53:40 -0800 (PST)
Received: from [24.216.152.109] (HELO westboro-1.world.std.com)
  by dc-mx07.cluster1.charter.net (CommuniGate Pro SMTP 3.5.3)
  with ESMTP id 8862044; Thu, 14 Feb 2002 12:05:59 -0500
Message-Id: <5.1.0.14.0.20020214155509.00a5d7a0@pop.theworld.com>
X-Sender: dpj@pop.theworld.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 14 Feb 2002 16:46:47 -0500
To: stephen.farrell@baltimore.ie
From: David Jablon <dpj@world.std.com>
Subject: Re: speke draft
Cc: ietf-sacred <ietf-sacred@imc.org>
In-Reply-To: <3C6BD1F1.347E75E7@baltimore.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>


Stephen,

Thanks for posting this.

Just for clarification, the letter [2] was sent to the IP Storage working group regarding
a question that the WG chair David Black addressed to Phoenix, and it wasn't intended
as a full IPR declaration for [1] or as the answer. It was merely a status report
acknowledging the request ... plus a few words from my sponsor.
For more context, see: http://www.pdl.cmu.edu/mailinglists/ips/mail/msg08716.html

Anyway, I think both documents are relevant to SACRED.
Also, the letter as forwarded omitted the contact information which is included below.

-- David

At 03:04 PM 2/14/02 +0000, Stephen Farrell wrote:
>Just FYI - a new I-D on speke [1] (with an accompanying 
>ipr "declaration" [2]).
>
>Stephen.
>
>[1] http://www.ietf.org/internet-drafts/draft-jablon-speke-00.txt
>[2] http://www.ietf.org/ietf/IPR/PHOENIX-SRP-RFC2945.txt

__________________________
David Jablon
CTO, Phoenix Technologies Ltd.
320 Norwood Park South
Norwood, MA  02062
david_jablon@phoenix.com
tel: +1 508 898 9024

a.k.a. dpj@world.std.com
www.IntegritySciences.com




From owner-ietf-sacred@mail.imc.org  Thu Feb 14 12:09:40 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27917
	for <sacred-archive@odin.ietf.org>; Thu, 14 Feb 2002 12:09:40 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id g1EH4kW10438
	for ietf-sacred-bks; Thu, 14 Feb 2002 09:04:46 -0800 (PST)
Received: from ocasey.baltimore.com (ocasey.baltimore.com [193.41.17.101])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g1EH4i310434
	for <ietf-sacred@imc.org>; Thu, 14 Feb 2002 09:04:44 -0800 (PST)
Received: from Baltimore-FW1 ([172.19.1.1])
	by ocasey.baltimore.com (8.11.6/8.9.3) with SMTP id g1EH4jU01702
	for <ietf-sacred@imc.org>; Thu, 14 Feb 2002 17:04:45 GMT
Received: from Baltimore-FW1 (wilde-i-1.ie.baltimore.com) by emeairlsw1.baltimore.com
 (Content Technologies SMTPRS 4.2.5) with SMTP id <T5911feceb60a99193517b@emeairlsw1.baltimore.com> for <ietf-sacred@imc.org>;
 Thu, 14 Feb 2002 17:00:01 +0000
Received: from baltimore.ie (wks140-4.ie.baltimore.com [10.153.4.140])
	by bobcat.baltimore.ie (8.9.3/8.9.3) with ESMTP id RAA31940
	for <ietf-sacred@imc.org>; Thu, 14 Feb 2002 17:04:42 GMT
Message-ID: <3C6BEDA9.5C2F9A37@baltimore.ie>
Date: Thu, 14 Feb 2002 17:02:33 +0000
From: Stephen Farrell <stephen.farrell@baltimore.ie>
Reply-To: stephen.farrell@baltimore.ie
Organization: Baltimore Technologies Ltd.
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-sacred <ietf-sacred@imc.org>
Subject: protocol draft "little" issues
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>
Content-Transfer-Encoding: 7bit



Folks,

The protocol draft contains the list of "minor" open issues 
below, that I'd like to get sorted.

If you have a suggestion/problem/wanna-chat about any of the 
suggested resolutions can you start a thread on the list over 
the next week or so? (Expressing your agreement is also fine,
since silence!=concensus:-)

   - If a server only supports up/down-load, then is SRP alone
     sufficient or MUST the server also support cTLS? (The latter
     according to the current text.)

          [cTLS is only a MUST for those that implement account
          management stuff.]

   - Meaning of empty string for credential selector?

          ["" means "all credentials", same as if the selector
          field is omitted entirely]

   - Does section 2.4 need changes?

          [this will be deleted as per list discussion, some
          "anti-DoS" text will be added to sec cons.]

   - Should we apply for a port number? (probably)

          [no.]

   - Should we define a URI scheme? (probably not)

          [no.]

   - Should the DTD or schema be normative? I'd usually go for the
     schema, but in this case the DTD seems much simpler.

          [since its much simpler let's make the DTD normative but
          keep the schema correct & up to date]

Ta,
Stephen.


-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 881 6716
39 Parkgate Street,                     fax: +353 1 881 7000
Dublin 8.                mailto:stephen.farrell@baltimore.ie
Ireland                             http://www.baltimore.com


From owner-ietf-sacred@mail.imc.org  Fri Feb 15 10:35:02 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08265
	for <sacred-archive@lists.ietf.org>; Fri, 15 Feb 2002 10:35:01 -0500 (EST)
Received: by above.proper.com (8.11.6/8.11.3) id g1FFTaS02905
	for ietf-sacred-bks; Fri, 15 Feb 2002 07:29:36 -0800 (PST)
Received: from tholian.rsasecurity.com (mail.rsasecurity.com [204.167.112.129])
	by above.proper.com (8.11.6/8.11.3) with SMTP id g1FFTY302901
	for <ietf-sacred@imc.org>; Fri, 15 Feb 2002 07:29:34 -0800 (PST)
Received: from sdtihq24.securitydynamics.com by tholian.rsasecurity.com
          via smtpd (for mail.imc.org [208.184.76.43]) with SMTP; 15 Feb 2002 15:28:58 UT
Received: from ebola.securitydynamics.com (ebola.securid.com [192.168.7.4])
	by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id KAA07251
	for <ietf-sacred@imc.org>; Fri, 15 Feb 2002 10:29:35 -0500 (EST)
Received: from spirit.dynas.se (localhost [127.0.0.1])
	by ebola.securitydynamics.com (8.10.2+Sun/8.9.1) with SMTP id g1FFTWa08448
	for <ietf-sacred@imc.org>; Fri, 15 Feb 2002 10:29:32 -0500 (EST)
Received: (qmail 24541 invoked from network); 15 Feb 2002 15:29:31 -0000
Received: from mnystrom-lap.d.dynas.se (HELO mnystrom-lap) (172.16.13.214)
  by spirit.dynas.se with SMTP; 15 Feb 2002 15:29:31 -0000
Date: Fri, 15 Feb 2002 16:29:35 +0100 (W. Europe Standard Time)
From: Magnus Nystrom <magnus@rsasecurity.com>
To: Stephen Farrell <stephen.farrell@baltimore.ie>
cc: ietf-sacred <ietf-sacred@imc.org>
Subject: Re: protocol draft "little" issues
In-Reply-To: <3C6BEDA9.5C2F9A37@baltimore.ie>
Message-ID: <Pine.WNT.4.43.0202151624080.1452-100000@mnystrom-lap>
X-X-Sender: magnus@spirit.dynas.se
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>


Hi Stephen,

A few comments (were I have a different view).

On Thu, 14 Feb 2002, Stephen Farrell wrote:

> Folks,
>
> The protocol draft contains the list of "minor" open issues
> below, that I'd like to get sorted.
>
> If you have a suggestion/problem/wanna-chat about any of the
> suggested resolutions can you start a thread on the list over
> the next week or so? (Expressing your agreement is also fine,
> since silence!=concensus:-)
>
>    - If a server only supports up/down-load, then is SRP alone
>      sufficient or MUST the server also support cTLS? (The latter
>      according to the current text.)
>
>           [cTLS is only a MUST for those that implement account
>           management stuff.]

In a scenario where a client wants to download a second set of
credentials, SRP would not be necessary. I'd say keep the current text.
Not too much to ask of a server to support both.

>    - Meaning of empty string for credential selector?
>
>           ["" means "all credentials", same as if the selector
>           field is omitted entirely]
>
>    - Does section 2.4 need changes?
>
>           [this will be deleted as per list discussion, some
>           "anti-DoS" text will be added to sec cons.]
>
>    - Should we apply for a port number? (probably)
>
>           [no.]

Yes. This is a new protocol.

>    - Should we define a URI scheme? (probably not)
>
>           [no.]
>
>    - Should the DTD or schema be normative? I'd usually go for the
>      schema, but in this case the DTD seems much simpler.
>
>           [since its much simpler let's make the DTD normative but
>           keep the schema correct & up to date]

The schema is my preference. I would also like it to be designed in a
"SAML-manner" or "XKMS-manner", i.e. basic building blocks "RequestType",
"ResponseType", that are extended for various types of requests and
responses. More general.

-- Magnus



From owner-ietf-sacred@mail.imc.org  Wed Feb 27 07:35:01 2002
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19243
	for <sacred-archive@odin.ietf.org>; Wed, 27 Feb 2002 07:35:01 -0500 (EST)
Received: by above.proper.com (8.11.6/8.11.3) id g1RCRCq13971
	for ietf-sacred-bks; Wed, 27 Feb 2002 04:27:12 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id g1RCRB313965
	for <ietf-sacred@imc.org>; Wed, 27 Feb 2002 04:27:12 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18766;
	Wed, 27 Feb 2002 07:27:09 -0500 (EST)
Message-Id: <200202271227.HAA18766@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-sacred@imc.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-sacred-protocol-bss-02.txt
Date: Wed, 27 Feb 2002 07:27:09 -0500
Sender: owner-ietf-sacred@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sacred/mail-archive/>
List-Unsubscribe: <mailto:ietf-sacred-request@imc.org?body=unsubscribe>
List-ID: <ietf-sacred.imc.org>


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Securely Available Credentials Working Group of the IETF.

	Title		: Securely Available Credentials Protocol
	Author(s)	: S. Farrell
	Filename	: draft-ietf-sacred-protocol-bss-02.txt
	Pages		: 20
	Date		: 26-Feb-02
	
This document describes an SRP-based protocol for securely available
credentials. Discussion of this draft is taking place on the SACRED
mailing list of the IETF SACRED working group (see
http://www.imc.org/ietf-sacred for subscription information).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sacred-protocol-bss-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-sacred-protocol-bss-02.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-sacred-protocol-bss-02.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:	<20020226131249.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sacred-protocol-bss-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sacred-protocol-bss-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--




