A Working Groups Wiki Page

[Nat Sakimura]

Indeed.

>From the spec works point of view, since a WG can always narrow the scope
but not exand,
it would be better to get it in the scope at the beginning. That's why I
have put it there.

We can always drop it later.

=nat

On Fri, Dec 5, 2008 at 10:14 AM, Breno de Medeiros <breno at google.com> wrote:

> On Thu, Dec 4, 2008 at 5:00 PM, Nat Sakimura <sakimura at gmail.com> wrote:
> > Hi Breno,
> >
> > I am hoping that the core spec will define public key based signature.
> > If it is done, CX is going to use it.
> > Dsig thing in the CX proposal is there just for the sake if it did not
> make
> > it into the core spec because it absolutely is a MUST for CX.
> > (Although, from the modularity point of view, it might be better to
> define
> > dsig separately and reference it from the core spec.)
>
> As long as you are aware of the issue, you can tackle this at a latter
> point by how you structure your deliverables.
>
> >
> > =nat
> >
> >
> > On Fri, Dec 5, 2008 at 2:20 AM, Breno de Medeiros <breno at google.com>
> wrote:
> >>
> >> Hi Nat,
> >>
> >> I see that as part of your scope you are discussing an OpenID D-Sign
> >> deliverable. Is this really necessary?
> >>
> >> For instance, the XRD 1.0 spec (which at this point is planned for
> >> incorporation into the OpenID spec by reference) will introduce a
> >> signature scheme for trust purposes. That will mean that a  a D-Sig
> >> algorithm will be part of the core spec.
> >>
> >> There is also some speculation that OpenID will support OAuth style
> >> signatures  (which include a public-key variant) for harmonization. If
> >> that happens there would be _two_ public-key signature schemes as part
> >> of the core spec.
> >>
> >> I understand the public-key signatures is a core requirement for a
> >> trust specification.  But I doubt there is a reason to re-invent such
> >> a scheme. Signature schemes are supposed to be somewhat generic, not
> >> purpose-specific. We should try to specify only a few of them, and
> >> probably the place to do that is the core OpenID spec.
> >>
> >> 2008/12/4 Nat Sakimura <sakimura at gmail.com>:
> >> > Thanks David,
> >> > I have put the CX page onto it.
> >> > Regards,
> >> > =nat
> >> >
> >> > On Thu, Dec 4, 2008 at 4:40 PM, David Recordon <
> drecordon at sixapart.com>
> >> > wrote:
> >> >>
> >> >> We now have a wiki page for Working Groups!
> >> >>  http://wiki.openid.net/Working_Groups
> >> >>
> >> >> I've listed the current PAPE WG as well as the groups that I know
> have
> >> >> been proposed.  I've also filled in the draft charter for the Auth
> 2.1
> >> >> group at http://wiki.openid.net/Working_Groups:Auth_2.1.
> >> >>
> >> >> If you're wanting to see a WG happen, please take this time to fill
> in
> >> >> it's draft charter so that members of this list can review it.  My
> >> >> goal would be to have all four of the proposed groups ready to be
> >> >> voted on by the Foundation Membership during the same period as the
> >> >> Board election -- one week from today -- so that they can all be
> >> >> created within the next two weeks.
> >> >>
> >> >> If you need help writing a charter, I'm happy to help.
> >> >>
> >> >> --David
> >> >>
> >> >> _______________________________________________
> >> >> specs mailing list
> >> >> specs at openid.net
> >> >> http://openid.net/mailman/listinfo/specs
> >> >
> >> >
> >> >
> >> > --
> >> > Nat Sakimura (=nat)
> >> > http://www.sakimura.org/en/
> >> >
> >> > _______________________________________________
> >> > specs mailing list
> >> > specs at openid.net
> >> > http://openid.net/mailman/listinfo/specs
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> --Breno
> >>
> >> +1 (650) 214-1007 desk
> >> +1 (408) 212-0135 (Grand Central)
> >> MTV-41-3 : 383-A
> >> PST (GMT-8) / PDT(GMT-7)
> >
> >
> >
> > --
> > Nat Sakimura (=nat)
> > http://www.sakimura.org/en/
> >
>
>
>
> --
> --Breno
>
> +1 (650) 214-1007 desk
> +1 (408) 212-0135 (Grand Central)
> MTV-41-3 : 383-A
> PST (GMT-8) / PDT(GMT-7)
>



-- 
Nat Sakimura (=nat)
http://www.sakimura.org/en/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs/attachments/20081217/dd862f1f/attachment-0001.htm>