Paul Hoffman | 1 Jun 03:24
Picon
Gravatar

Re: Structured data over TCP?

At 12:50 PM -0500 5/29/09, Nicolas Williams wrote:
>Therefore, if you have a volatile API then you need to have a way to do
>versioning if you use JSON.  Then again, if you have data that has a
>long at-rest lifetime, then you really want to specify its schema
>somewhere, and once you're at that point you're better off with XML.

What is the problem with starting your JSON with a string that identifies the schema? { {"uid" : "97ad72a2"}
{ "count" : 42 } .... }. A parser can look for the first item in the structure and be sure that it exactly
matches what it expects.
Patrik Fältström | 1 Jun 08:36
Picon
Favicon
Gravatar

Re: Structured data over TCP?

On 1 jun 2009, at 03.24, Paul Hoffman wrote:

> At 12:50 PM -0500 5/29/09, Nicolas Williams wrote:
>> Therefore, if you have a volatile API then you need to have a way  
>> to do
>> versioning if you use JSON.  Then again, if you have data that has a
>> long at-rest lifetime, then you really want to specify its schema
>> somewhere, and once you're at that point you're better off with XML.
>
> What is the problem with starting your JSON with a string that  
> identifies the schema? { {"uid" : "97ad72a2"} { "count" :  
> 42 } .... }. A parser can look for the first item in the structure  
> and be sure that it exactly matches what it expects.

Even easier, you can have:

{ 'version' : 4711, 'data' : { 'foo' : 11, 'bar' : 'cookie' }}

And then check for "version". And if "version" does not exist, bail.

    paf
Alexey Melnikov | 2 Jun 11:11
Favicon

Re: TLS server identity verification

Alexey Melnikov wrote:

> Folks,
> The issue of a document describing recommended text/template for 
> server identity verification procedure came up again while talking 
> about advancing EPP.
>
> As an AD, I would really like for draft-hodges-server-ident-check to 
> be published as an RFC. And I know that Chris was keen on this as well.
> Jeff/Bob, do you have any cycles to work on this?

As I've heard no response from the authors and lots of support from the 
community to work on this, I've asked Kurt Zeilenga and Peter 
Saint-Andre to take over editing of the document.
=JeffH | 2 Jun 17:31

Re: TLS server identity verification

 > As I've heard no response from the authors and lots of support from the
 > community to work on this, I've asked Kurt Zeilenga and Peter
 > Saint-Andre to take over editing of the document.

That's fine, those are good hands to place it into. Apologies for not 
responding sooner, I've been buried with other topics of late due to my new 
position. I'll try to contribute to this draft as I can as it moves forward.

thanks,

=JeffH
tom.petch | 3 Jun 09:30

Re: TLS server identity verification

----- Original Message ----- 
From: "Alexey Melnikov" <alexey.melnikov <at> isode.com>
To: "Apps Discuss" <discuss <at> apps.ietf.org>
Cc: "=JeffH" <Jeff.Hodges <at> KingsMountain.com>
Sent: Tuesday, June 02, 2009 11:11 AM
Subject: Re: TLS server identity verification

> Alexey Melnikov wrote:
> 
> > Folks,
> > The issue of a document describing recommended text/template for 
> > server identity verification procedure came up again while talking 
> > about advancing EPP.
> >
> > As an AD, I would really like for draft-hodges-server-ident-check to 
> > be published as an RFC. And I know that Chris was keen on this as well.
> > Jeff/Bob, do you have any cycles to work on this?
> 
> As I've heard no response from the authors and lots of support from the 
> community to work on this, I've asked Kurt Zeilenga and Peter 
> Saint-Andre to take over editing of the document.

What comes next?

Will they re-issue it?  Will it be put up for adoption as an ietf document?
Or do you want to go straight into comments on the I-D as is?

Tom Petch

> _______________________________________________
(Continue reading)

Peter Saint-Andre | 3 Jun 16:43
Favicon

Re: TLS server identity verification


On 6/3/09 1:30 AM, tom.petch wrote:
> ----- Original Message ----- 
> From: "Alexey Melnikov" <alexey.melnikov <at> isode.com>
> To: "Apps Discuss" <discuss <at> apps.ietf.org>
> Cc: "=JeffH" <Jeff.Hodges <at> KingsMountain.com>
> Sent: Tuesday, June 02, 2009 11:11 AM
> Subject: Re: TLS server identity verification
> 
> 
>> Alexey Melnikov wrote:
>>
>>> Folks,
>>> The issue of a document describing recommended text/template for 
>>> server identity verification procedure came up again while talking 
>>> about advancing EPP.
>>>
>>> As an AD, I would really like for draft-hodges-server-ident-check to 
>>> be published as an RFC. And I know that Chris was keen on this as well.
>>> Jeff/Bob, do you have any cycles to work on this?
>> As I've heard no response from the authors and lots of support from the 
>> community to work on this, I've asked Kurt Zeilenga and Peter 
>> Saint-Andre to take over editing of the document.
> 
> What comes next?
> 
> Will they re-issue it?  Will it be put up for adoption as an ietf document?
> Or do you want to go straight into comments on the I-D as is?

Kurt and I will work to produce an updated I-D soon, incorporating the
(Continue reading)

Alexey Melnikov | 3 Jun 21:39
Favicon

Re: TLS server identity verification

tom.petch wrote:

>----- Original Message ----- 
>From: "Alexey Melnikov" <alexey.melnikov <at> isode.com>
>To: "Apps Discuss" <discuss <at> apps.ietf.org>
>Cc: "=JeffH" <Jeff.Hodges <at> KingsMountain.com>
>Sent: Tuesday, June 02, 2009 11:11 AM
>Subject: Re: TLS server identity verification
>  
>
>>Alexey Melnikov wrote:
>>    
>>
>>>Folks,
>>>The issue of a document describing recommended text/template for 
>>>server identity verification procedure came up again while talking 
>>>about advancing EPP.
>>>
>>>As an AD, I would really like for draft-hodges-server-ident-check to 
>>>be published as an RFC. And I know that Chris was keen on this as well.
>>>Jeff/Bob, do you have any cycles to work on this?
>>>      
>>>
>>As I've heard no response from the authors and lots of support from the 
>>community to work on this, I've asked Kurt Zeilenga and Peter 
>>Saint-Andre to take over editing of the document.
>>    
>>
>What comes next?
>
(Continue reading)

Peter Saint-Andre | 3 Jun 21:53
Favicon

Re: TLS server identity verification


On 6/3/09 1:39 PM, Alexey Melnikov wrote:

>> What comes next?
>>
>> Will they re-issue it?  Will it be put up for adoption as an ietf
>> document?
>>  
>>
> New editors told me that the first version is just going to be a
> refresh. Then they will work on updating it based on comments.

Correct. Kurt and I will work to post a refreshed version this week.
Since it's only a refresh it won't take much time. :)

Peter

--
Peter Saint-Andre
https://stpeter.im/

Peter Saint-Andre | 4 Jun 00:34
Favicon

[Fwd: I-D Action:draft-saintandre-tls-server-id-check-00.txt]


FYI. All I did was update the references, change the title slightly, and
update the authors. Feedback is welcome before we publish a version with
more significant modifications.

Peter

-------- Original Message --------
Subject: I-D Action:draft-saintandre-tls-server-id-check-00.txt
Date: Wed,  3 Jun 2009 15:30:02 -0700 (PDT)
From: Internet-Drafts <at> ietf.org
Reply-To: internet-drafts <at> ietf.org
To: i-d-announce <at> ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title           : Best Practices for Checking of Server Identities in
the Context of Transport Layer Security (TLS)
	Author(s)       : P. Saint-Andre, et al.
	Filename        : draft-saintandre-tls-server-id-check-00.txt
	Pages           : 7
	Date            : 2009-06-03

This document specifies the how an entity establishing a TLS
connection, or other PKI-based interaction, with a server should
verify the server identity.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-saintandre-tls-server-id-check-00.txt
(Continue reading)

Simon Josefsson | 4 Jun 10:29
Favicon
Gravatar

Re: [Fwd: I-D Action:draft-saintandre-tls-server-id-check-00.txt]

Peter Saint-Andre <stpeter <at> stpeter.im> writes:

> FYI. All I did was update the references, change the title slightly, and
> update the authors. Feedback is welcome before we publish a version with
> more significant modifications.

Generally, I agree a document like this is needed.  Some suggestions:

1) Define all terminology in section 2.  The term "reference identity"
is defined in section 3 but used in other sections too.

2) Re 3.1, should the reference identity be considered a stored string
wrt IDNA?  As I understand what reference identity refers to, it seems
like a query string to me.

Thanks,
/Simon

Gmane