Re: [Isms] pre11 comments
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Isms] pre11 comments



----- Original Message -----
From: "Juergen Schoenwaelder" <j.schoenwaelder at jacobs-university.de>
To: "Jeffrey Hutzelman" <jhutz+ at cmu.edu>
Cc: <isms at ietf.org>; <jhutz at cmu.edu>
Sent: Thursday, July 24, 2008 9:17 AM
Subject: Re: [Isms] pre11 comments


> On Wed, Jul 23, 2008 at 02:07:22AM -0400, Jeffrey Hutzelman wrote:
>
> > [...] In order to simplify this somewhat and also address what I believe
> > is Wes's concern (which has nothing to do with securityLevel), I'd like
> > to propose a strawman.  Specifically, I propose that for TSM, the
> > securityName always take the form "TM:name", where TM is a token
> > indicating the secure transport model in use and name is a
> > transport-specific ID.  Obviously we'd need an IANA registry of possible
> > values for the TM token, and a new value would need to be allocated for
> > each token.
>
> Speaking as technical contributor...
>
> Assuming the TM allows operators to configure "name" mappings. Isn't
> that sufficient? Do we really have to enforce a specific mapping or
> are we not better served by simply discussing the issue in the
> documents and suggesting certain configurations options addressing the
> issue?
>
I agree; TM is the place to do the mapping.  This is a TM related issue and we
should fix it close to where the problem arises, namely in the TM.

(And, at the risk of being repetitive, there is a problem with a mapping table
in the SM with the ASIs as currently defined; fixable, but requiring a change to
the ASIs).

Tom Petch

> For some secure transports (e.g. TLS and DTLS), there might be valid
> reasons to not make a difference and so I prefer a clear separation of
> mechanism and policy here.
>
> /js
>
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> _______________________________________________
> Isms mailing list
> Isms at ietf.org
> https://www.ietf.org/mailman/listinfo/isms

_______________________________________________
Isms mailing list
Isms at ietf.org
https://www.ietf.org/mailman/listinfo/isms



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.