IPR-WG Discussion Archive - Thread Index
[Prev Page] [Next Page] [Date Index]
[IETF Announcements Archive]
- Re: SPARC Author Addendum compatibility, (continued)
- Re: SPARC Author Addendum compatibility,
Brian E Carpenter
- Re: SPARC Author Addendum compatibility,
John C Klensin
- Re: SPARC Author Addendum compatibility,
todd glassey
- Re: SPARC Author Addendum compatibility,
Simon Josefsson
- Re: SPARC Author Addendum compatibility,
John C Klensin
- Re: SPARC Author Addendum compatibility,
Joel M. Halpern
- Re: SPARC Author Addendum compatibility,
John C Klensin
- Re: SPARC Author Addendum compatibility,
Brian E Carpenter
- Re: SPARC Author Addendum compatibility,
TS Glassey
- RE: SPARC Author Addendum compatibility,
Lawrence Rosen
- RE: SPARC Author Addendum compatibility,
John C Klensin
- RE: SPARC Author Addendum compatibility,
Lawrence Rosen
- RE: SPARC Author Addendum compatibility,
John C Klensin
- Re: SPARC Author Addendum compatibility,
todd glassey
- Re: SPARC Author Addendum compatibility,
Brian E Carpenter
- Re: SPARC Author Addendum compatibility,
Bill Fardy
- Re: SPARC Author Addendum compatibility,
John C Klensin
- Re: SPARC Author Addendum compatibility,
TS Glassey
- Re: SPARC Author Addendum compatibility,
TS Glassey
- Re: SPARC Author Addendum compatibility,
todd glassey
- Review of outbound-03: Major issues,
Simon Josefsson
- Review of outbound-03: Minor issues,
Simon Josefsson
- An example of the outbound rights problem,
Sam Hartman
- Re: An example of the outbound rights problem,
Harald Tveit Alvestrand
- Re: An example of the outbound rights problem,
Simon Josefsson
- Re: An example of the outbound rights problem,
Brian E Carpenter
- Re: An example of the outbound rights problem,
Joel M. Halpern
- Re: An example of the outbound rights problem,
Simon Josefsson
- Re: An example of the outbound rights problem,
Harald Tveit Alvestrand
- Re: An example of the outbound rights problem,
Brian E Carpenter
- Re: An example of the outbound rights problem,
Harald Tveit Alvestrand
- Re: An example of the outbound rights problem,
Simon Josefsson
- Re: An example of the outbound rights problem,
Harald Tveit Alvestrand
- Re: An example of the outbound rights problem,
todd glassey
- Re: An example of the outbound rights problem,
todd glassey
- Issues from the tracker that I believe are resolved,
Harald Tveit Alvestrand
- Two issues closed,
Harald Tveit Alvestrand
- Collective rights: Quote from US law,
Harald Tveit Alvestrand
- I'm stepping down as chair,
Steven M. Bellovin
- Agenda for our Chicago meeting,
Harald Tveit Alvestrand
- Incoming - software licenses,
Black_David
- WG LAST CALL on the -outgoing document,
Harald Tveit Alvestrand
- LC ISSUE: OUTGOING Sections 2 and 3: Editorial [Re: WG LAST CALL on the -outgoing document],
Brian E Carpenter
- LC ISSUE: OUTGOING Section 6.3: vague s/w licensing guidance,
Black_David
- #1500 Outgoing LC 6.3: SW licensing,
Harald Alvestrand
- Re: LC ISSUE: OUTGOING Section 6.3: vague s/w licensing guidance,
Simon Josefsson
- RE: LC ISSUE: OUTGOING Section 6.3: vague s/w licensing guidance,
Black_David
- Re: LC ISSUE: OUTGOING Section 6.3: vague s/w licensing guidance,
Brian E Carpenter
- RE: LC ISSUE: OUTGOING Section 6.3: vague s/w licensing guidance,
Black_David
- RE: LC ISSUE: OUTGOING Section 6.3: vague s/w licensing guidance,
Ted Hardie
- RE: LC ISSUE: OUTGOING Section 6.3: vague s/w licensing guidance,
Black_David
- RE: LC ISSUE: OUTGOING Section 6.3: vague s/w licensing guidance,
John C Klensin
- Re: LC ISSUE: OUTGOING Section 6.3: vague s/w licensing guidance,
Brian E Carpenter
- RE: LC ISSUE: OUTGOING Section 6.3: vague s/w licensing guidance,
Black_David
- Re: LC ISSUE: OUTGOING Section 6.3: vague s/w licensing guidance,
Simon Josefsson
- RE: LC ISSUE: OUTGOING Section 6.3: vague s/w licensing guidance,
Black_David
- Message not available
- RE: LC ISSUE: OUTGOING Section 6.3: vague s/w licensing guidance,
Joel M. Halpern
I-D ACTION:draft-ietf-ipr-3978-incoming-01.txt,
Internet-Drafts
2nd response - the usual email disclaimer nonsense, was LTANS WG Last Call,
todd glassey
Re: LTANS WG Last Call on draft-ietf-ltans-ers-scvp-03.txt,
todd glassey
- Re: LTANS WG Last Call on draft-ietf-ltans-ers-scvp-03.txt,
Harald Alvestrand
- Re: LTANS WG Last Call on draft-ietf-ltans-ers-scvp-03.txt,
todd glassey
- Re: LTANS WG Last Call on draft-ietf-ltans-ers-scvp-03.txt,
Graham Murray
- Re: LTANS WG Last Call on draft-ietf-ltans-ers-scvp-03.txt,
todd glassey
- Re: the usual email disclaimer nonsense, was LTANS WG Last Call,
John Levine
- Re: the usual email disclaimer nonsense, was LTANS WG Last Call,
C.T. Aiken
- Re: the usual email disclaimer nonsense, was LTANS WG Last Call,
Bill Fardy
- Re: the usual email disclaimer nonsense, was LTANS WG Last Call,
TS Glassey
- Re: the usual email disclaimer nonsense, was LTANS WG Last Call,
Brian E Carpenter
- RE: LTANS WG Last Call on draft-ietf-ltans-ers-scvp-03.txt,
Tobias Gondrom
- Re: LTANS WG Last Call on draft-ietf-ltans-ers-scvp-03.txt,
todd glassey
New EU Anti-Copyright Violation Rule info...,
todd glassey
Effective vs intended handling of patent encumbrance in IETF wg and IESG,
Thierry Moreau
Admin note: The IPR design team,
Harald Alvestrand
I have requested a 2-hour slot for Chicago,
Harald Tveit Alvestrand
Re: Section 6.5: Additional Licenses for IETF Contributions,
Todd Glassey
Software as Goods... - UCC Article 9, def #44,
todd glassey
- Re: Software as Goods... - UCC Article 9, def #44,
Harald Alvestrand
- Re: Software as Goods... - UCC Article 9, def #44,
todd glassey
- <Possible follow-ups>
- Re: Software as Goods... - UCC Article 9, def #44,
Todd Glassey
- Re: Software as Intangible Bit Streams -- News at 11,
Don Armstrong
- Re: Software as Goods... - UCC Article 9, def #44,
Graham Murray
- Form of incorporation of organizations (Re: Software as Goods... - UCC Article 9, def #44),
Harald Alvestrand
- Re: Form of incorporation of organizations (Re: Software as Goods... - UCC Article 9, def #44),
todd glassey
- RE: Form of incorporation of organizations (Re: Software asGoods... - UCC Article 9, def #44),
Black_David
- Re: Form of incorporation of organizations (Re: Software asGoods... - UCC Article 9, def #44),
todd glassey
- RE: Form of incorporation of organizations (Re: Software asGoods...- UCC Article 9, def #44),
Black_David
- Re: Form of incorporation of organizations (Re: Software asGoods...- UCC Article 9, def #44),
todd glassey
- RE: Form of incorporation of organizations (Re: Software asGoods...- UCC Article 9, def #44),
Black_David
- Re: Form of incorporation of organizations (Re: Software asGoods...- UCC Article 9, def #44),
todd glassey
- RE: Form of incorporation of organizations (Re: Software asGoods...- UCC Article 9, def #44),
Contreras, Jorge
- RE: Form of incorporation of organizations (Re: Software asGoods... - UCC Article 9, def #44),
Contreras, Jorge
- Re: Form of incorporation of organizations (Re: Software asGoods... - UCC Article 9, def #44),
TS Glassey
- Re: Form of incorporation of organizations (Re: Software asGoods... - UCC Article 9, def #44),
todd glassey
- Typo - Re: Form of incorporation of organizations (Re: Software asGoods...- UCC Article 9, def #44),
todd glassey
- Re: Software as Goods... - UCC Article 9, def #44,
Stephane Bortzmeyer
- Re: Software as Goods... - UCC Article 9, def #44,
John C Klensin
I-D ACTION:draft-ietf-ipr-outbound-rights-03.txt,
Internet-Drafts
- Re: I-D ACTION:draft-ietf-ipr-outbound-rights-03.txt,
Brian E Carpenter
- Section 6.5: Additional Licenses for IETF Contributions,
Simon Josefsson
- Re: Section 6.5: Additional Licenses for IETF Contributions,
John C Klensin
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Simon Josefsson
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Brian E Carpenter
- Re: Section 6.5: Additional Licenses for IETF Contributions,
todd glassey
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Don Armstrong
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Joel M. Halpern
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Simon Josefsson
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Harald Alvestrand
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Don Armstrong
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Simon Josefsson
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Brian E Carpenter
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Frank Ellermann
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Brian E Carpenter
- Re: Section 6.5: Additional Licenses for IETF Contributions,
John C Klensin
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Frank Ellermann
- Re: Section 6.5: Additional Licenses for IETF Contributions,
John C Klensin
- Re: Section 6.5: Additional Licenses for IETF Contributions,
todd glassey
- Re: Section 6.5: Additional Licenses for IETF Contributions,
John C Klensin
- Re: Section 6.5: Additional Licenses for IETF Contributions,
todd glassey
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Don Armstrong
- Re: Section 6.5: Additional Licenses for IETF Contributions,
todd glassey
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Bill Fardy
- Re: Section 6.5: Additional Licenses for IETF Contributions,
todd glassey
- Re: Section 6.5: Additional Licenses for IETF Contributions,
todd glassey
- Re: Section 6.5: Additional Licenses for IETF Contributions,
todd glassey
- Re: Section 6.5: Additional Licenses for IETF Contributions,
Frank Ellermann
- Re: Section 6.5: Additional Licenses for IETF Contributions,
todd glassey
- <Possible follow-ups>
- Fwd: I-D ACTION:draft-ietf-ipr-outbound-rights-03.txt,
Joel M. Halpern
Outbound Rights Document,
Joel M. Halpern
BCP0079 RFC 4879 on Clarification of the Third Party Disclosure Procedure in RFC 3979,
rfc-editor
Re: Withdrawal of Approval and Second Last Call: draft-housley-tls-authz-extns,
Todd Glassey
Re: Withdrawal of Approval and Second Last Call: draft-housley-tls-authz-extns,
todd glassey
recourse if our rules are violated?,
Steven M. Bellovin
- Re: recourse if our rules are violated?,
John C Klensin
- Re: recourse if our rules are violated?,
Joel M. Halpern
- <Possible follow-ups>
- Re: recourse if our rules are violated?,
Todd Glassey
- Re: recourse if our rules are violated?,
Scott O. Bradner
- Re: recourse if our rules are violated?,
Brian E Carpenter
- Re: recourse if our rules are violated?,
John C Klensin
- Re: recourse if our rules are violated?,
Brian E Carpenter
- Re: recourse if our rules are violated?,
John C Klensin
- Re: recourse if our rules are violated?,
Frank Ellermann
- Re: recourse if our rules are violated?,
Harald Tveit Alvestrand
- Re: recourse if our rules are violated?,
Brian E Carpenter
- Re: recourse if our rules are violated?,
todd glassey
- Re: recourse if our rules are violated?,
Frank Ellermann
- Re: recourse if our rules are violated?,
Simon Josefsson
- Re: recourse if our rules are violated?,
todd glassey
- Re: recourse if our rules are violated?,
Harald Alvestrand
- Re: recourse if our rules are violated?,
todd glassey
- Re: recourse if our rules are violated?,
Frank Ellermann
- Re: recourse if our rules are violated?,
Harald Alvestrand
- Re: recourse if our rules are violated?,
todd glassey
- Explanantion - Re: recourse if our rules are violated?,
todd glassey
- Re: recourse if our rules are violated?,
todd glassey
- Re: recourse if our rules are violated?,
Frank Ellermann
- Re: recourse if our rules are violated?,
todd glassey
- Re: recourse if our rules are violated?,
todd glassey
- Re: recourse if our rules are violated?,
Harald Alvestrand
- Re: recourse if our rules are violated?,
Frank Ellermann
- Re: recourse if our rules are violated?,
Brian E Carpenter
- Re: recourse if our rules are violated?,
Scott W Brim
- Re: recourse if our rules are violated?,
Frank Ellermann
- Re: recourse if our rules are violated?,
Brian E Carpenter
- Re: recourse if our rules are violated?,
todd glassey
- Re: recourse if our rules are violated?,
Frank Ellermann
- Re: recourse if our rules are violated?,
Tom Petch
- Original Filing Intent - was Re: recourse if our rules are violated?,
todd glassey
- Re: recourse if our rules are violated?,
Frank Ellermann
- Re: recourse if our rules are violated?,
John C Klensin
- Re: recourse if our rules are violated?,
Simon Josefsson
- Re: recourse if our rules are violated?,
todd glassey
- Re: recourse if our rules are violated?,
todd glassey
- RE: recourse if our rules are violated?,
David B Harrington
- RE: recourse if our rules are violated?,
John C Klensin
- Re: recourse if our rules are violated?,
todd glassey
- Re: recourse if our rules are violated?,
Todd Glassey
- Re: recourse if our rules are violated?,
Todd Glassey
- Re: recourse if our rules are violated?,
Scott O. Bradner
Senders to this mailing list,
Harald Alvestrand
RE: Copyright, Privacy, Confidentiality Statements on Submissions to the IETF,
Contreras, Jorge
Copyright, Privacy, Confidentiality Statements on Submissions to the IETF,
Russ Housley
Contributions on "other lists",
Frank Ellermann
DRAFT minutes from Prague IPR WG meeting,
Harald Alvestrand
A guide to the IETF's process documents,
Harald Tveit Alvestrand
Agenda slides uploaded to proceedings,
Harald Tveit Alvestrand
ISSUE: resolve issues in tracker,
Simon Josefsson
Question about timeline,
Simon Josefsson
Lawyer's advice on boilerplate in RFCs and I-Ds,
Harald Tveit Alvestrand
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Frank Ellermann
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Brian E Carpenter
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Frank Ellermann
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Brian E Carpenter
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Frank Ellermann
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
John C Klensin
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Steven M. Bellovin
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
todd glassey
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Steven M. Bellovin
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
todd glassey
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Steven M. Bellovin
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
todd glassey
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Harald Tveit Alvestrand
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
todd glassey
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Harald Tveit Alvestrand
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Frank Ellermann
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
John C Klensin
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Simon Josefsson
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
John C Klensin
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Simon Josefsson
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Brian E Carpenter
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
todd glassey
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Frank Ellermann
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
todd glassey
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Simon Josefsson
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Colin Perkins
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Bill Fenner
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
C. M. Heard
- RE: Lawyer's advice on boilerplate in RFCs and I-Ds,
David B Harrington
- RE: Lawyer's advice on boilerplate in RFCs and I-Ds,
C. M. Heard
- RFC 4071 (Re: Lawyer's advice on boilerplate in RFCs and I-Ds),
Harald Alvestrand
- Re: RFC 4071 (Re: Lawyer's advice on boilerplate in RFCs and I-Ds),
todd glassey
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Brian E Carpenter
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Russ Housley
- RFC 4071 (Re: Lawyer's advice on boilerplate in RFCs and I-Ds),
Harald Tveit Alvestrand
- Re: RFC 4071 (Re: Lawyer's advice on boilerplate in RFCs and I-Ds),
Harald Tveit Alvestrand
- Message not available
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
todd glassey
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Steven M. Bellovin
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Simon Josefsson
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
John C Klensin
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Frank Ellermann
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Frank Ellermann
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Simon Josefsson
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Frank Ellermann
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Brian E Carpenter
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
todd glassey
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Brian E Carpenter
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Harald Tveit Alvestrand
- Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Pekka Savola
Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
todd glassey
<Possible follow-ups>
Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Harald Tveit Alvestrand
Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Todd Glassey
Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Todd Glassey
Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Todd Glassey
Re: Lawyer's advice on boilerplate in RFCs and I-Ds,
Todd Glassey
Agenda sketch, IPR WG meeting in Prague,
Harald Alvestrand
- Outgoing issues (was: Re: Agenda sketch, IPR WG meeting in Prague),
Simon Josefsson
- Re: Outgoing issues (was: Re: Agenda sketch, IPR WG meeting in Prague),
Joel Halpern
- Re: Outgoing issues,
Harald Alvestrand
- Re: Outgoing issues,
Harald Alvestrand
- ISSUE: I-Ds talking about their own consensus are not ready for Last Call (was: Outgoing issues),
Frank Ellermann
- Re: ISSUE: I-Ds talking about their own consensus are not ready for Last Call (was: Outgoing issues),
Harald Tveit Alvestrand
- Re: ISSUE: I-Ds talking about their own consensus are not ready for Last Call,
Frank Ellermann
- Re: ISSUE: I-Ds talking about their own consensus are not ready for Last Call,
Joel M. Halpern
- Re: ISSUE: I-Ds talking about their own consensus are not ready for Last Call,
Scott W Brim
- Re: ISSUE: I-Ds talking about their own consensus are not ready for Last Call,
Brian E Carpenter
- Re: ISSUE: I-Ds talking about their own consensus are not ready for Last Call,
Frank Ellermann
- Re: ISSUE: I-Ds talking about their own consensus are not ready for Last Call,
todd glassey
- Re: ISSUE: I-Ds talking about their own consensus are not ready for Last Call,
Joel M. Halpern
- Re: ISSUE: I-Ds talking about their own consensus are not ready for Last Call,
John C Klensin
- ISSUE: adopt RFC 4693 section 2.2 paragraph 5 (was: outgoing issues),
Frank Ellermann
- Re: ISSUE: adopt RFC 4693 section 2.2 paragraph 5,
Brian E Carpenter
- Re: ISSUE: adopt RFC 4693 section 2.2 paragraph 5,
Steven M. Bellovin
- Re: ISSUE: adopt RFC 4693 section 2.2 paragraph 5,
Harald Tveit Alvestrand
- Re: ISSUE: adopt RFC 4693 section 2.2 paragraph 5,
Frank Ellermann
- Re: ISSUE: adopt RFC 4693 section 2.2 paragraph 5,
Joel M. Halpern
- Re: ISSUE: adopt RFC 4693 section 2.2 paragraph 5,
Frank Ellermann
- Re: ISSUE: adopt RFC 4693 section 2.2 paragraph 5,
Simon Josefsson
- Re: ISSUE: adopt RFC 4693 section 2.2 paragraph 5,
Brian E Carpenter
- Re: ISSUE: adopt RFC 4693 section 2.2 paragraph 5,
Simon Josefsson
- Re: ISSUE: adopt RFC 4693 section 2.2 paragraph 5,
Frank Ellermann
- Re: ISSUE: adopt RFC 4693 section 2.2 paragraph 5,
Henrik Levkowetz
- IONs on the tool server (was: ISSUE: adopt RFC 4693 section 2.2 paragraph 5),
Frank Ellermann
- Re: Outgoing issues,
Brian E Carpenter
Outgoing Terminology,
Joel M. Halpern
I-D ACTION:draft-ietf-ipr-3978-incoming-00.txt,
Internet-Drafts
Call for issues, -outgoing document,
Harald Alvestrand
Request for input (patchwork RFCs),
Lucy Lynch
IPR WG session requested for Prague,
Harald Tveit Alvestrand
FW: Last Call: draft-heard-rfc4181-update (RFC 4181 Update to Recognize the IETF Trust) to BCP,
C. M. Heard
Outbound Rights Issues,
Joel M. Halpern
IANA-maintained MIB copyright question,
Bill Fenner
Good reference article on Fair Use... and Copyright under Creative Commons.,
todd glassey
I-D ACTION:draft-ietf-ipr-outbound-rights-02.txt,
Internet-Drafts
- <Possible follow-ups>
- Fwd: I-D ACTION:draft-ietf-ipr-outbound-rights-02.txt,
Joel M. Halpern
- Comments on draft-ietf-ipr-outbound-rights-02.txt,
Simon Josefsson
- Re: Comments on draft-ietf-ipr-outbound-rights-02.txt,
Joel M. Halpern
- Re: Comments on draft-ietf-ipr-outbound-rights-02.txt,
Simon Josefsson
- Split between -inbound and -outbound (Re: Comments on draft-ietf-ipr-outbound-rights-02.txt),
Harald Tveit Alvestrand
- Re: Split between -inbound and -outbound (Re: Comments on draft-ietf-ipr-outbound-rights-02.txt),
Simon Josefsson
- RE: Split between -inbound and -outbound (Re: Comments ondraft-ietf-ipr-outbound-rights-02.txt),
Contreras, Jorge
- Re: Comments on draft-ietf-ipr-outbound-rights-02.txt,
Frank Ellermann
- Re: Comments on draft-ietf-ipr-outbound-rights-02.txt,
Joel M. Halpern
- Re: Comments on draft-ietf-ipr-outbound-rights-02.txt,
Frank Ellermann
- Re: Comments on draft-ietf-ipr-outbound-rights-02.txt,
Simon Josefsson
- Appeals [Re: Comments on draft-ietf-ipr-outbound-rights-02.txt],
Brian E Carpenter
- Message not available
- Re: Appeals [Re: Comments on draft-ietf-ipr-outbound-rights-02.txt],
Brian E Carpenter
- Re: Comments on draft-ietf-ipr-outbound-rights-02.txt,
Frank Ellermann
- Restriction on the right to modify (Re: Comments on draft-ietf-ipr-outbound-rights-02.txt),
Harald Tveit Alvestrand
- Re: Restriction on the right to modify,
Frank Ellermann
- Re: Restriction on the right to modify (Re: Comments on draft-ietf-ipr-outbound-rights-02.txt),
Simon Josefsson
- Re: Restriction on the right to modify (Re: Comments on draft-ietf-ipr-outbound-rights-02.txt),
Steven M. Bellovin
- Re: Restriction on the right to modify (Re: Comments on draft-ietf-ipr-outbound-rights-02.txt),
Brian E Carpenter
Re: Case study: SHA2,
Scott O. Bradner
FYI: 3979 update (was: I-D ACTION:draft-lynch-execd-tasks-00.txt),
Frank Ellermann
IETF IP Contribution Policy,
Lawrence Rosen
Protocol Action: 'Clarification of the 3rd Party Disclosure procedure in RFC 3979' to BCP,
The IESG
Re: IETF Trust FAQ,
Brian E Carpenter
- Re: IETF Trust FAQ,
Simon Josefsson
- Re: IETF Trust FAQ,
Brian E Carpenter
- Re: IETF Trust FAQ,
Simon Josefsson
- Re: IETF Trust FAQ,
Harald Alvestrand
- RE: IETF Trust FAQ,
Lawrence Rosen
- RE: IETF Trust FAQ,
Contreras, Jorge
- Re: IETF Trust FAQ,
todd glassey
- RE: IETF Trust FAQ,
Contreras, Jorge
- RE: IETF Trust FAQ,
Lawrence Rosen
- Patent Licenses for Code in RFCs?,
Contreras, Jorge
- Re: Patent Licenses for Code in RFCs?,
Brian E Carpenter
- Granting rights that you do not have,
Simon Josefsson
- Re: IETF Trust FAQ,
Steven M. Bellovin
- RE: IETF Trust FAQ,
Lawrence Rosen
- Patent licenses (was: IETF Trust FAQ),
Frank Ellermann
- Re: Patent licenses (was: IETF Trust FAQ),
todd glassey
- IETF Patent policy (was RE: IETF Trust FAQ),
Ted Hardie
- RE: IETF Patent policy (was RE: IETF Trust FAQ),
Lawrence Rosen
- RE: IETF Patent policy (was RE: IETF Trust FAQ),
Ted Hardie
- RE: IETF Patent policy (was RE: IETF Trust FAQ),
John C Klensin
- Re: IETF Patent policy (was RE: IETF Trust FAQ),
Mukundan R
- Re: IETF Patent policy (was RE: IETF Trust FAQ),
todd glassey
- Re: IETF Trust FAQ,
Harald Alvestrand
- RE: IETF Trust FAQ,
Lawrence Rosen
- ADMIN: One topic per subject line (Re: IETF Trust FAQ),
Harald Alvestrand
- Purpose of this WG [Re: IETF Trust FAQ],
Brian E Carpenter
- Re: IETF Trust FAQ,
todd glassey
- Re: IETF Trust FAQ,
todd glassey
- Re: IETF Trust FAQ,
Stephane Bortzmeyer
- Patented RFC Code,
Contreras, Jorge
- Re: Patented RFC Code,
Stephane Bortzmeyer
- RE: Patented RFC Code,
Contreras, Jorge
- Copyrighted RFC Code,
Simon Josefsson
- Re: Copyrighted RFC Code,
Harald Alvestrand
- Re: Patented RFC Code,
todd glassey
- RE: Patented RFC Code,
Lawrence Rosen
- Re: Patented RFC Code,
Harald Alvestrand
- Re: Patented RFC Code,
Frank Ellermann
- Re: Patented RFC Code,
John C Klensin
- Re: Patented RFC Code,
todd glassey
- Re: Patented RFC Code,
Frank Ellermann
- Re: Patented RFC Code,
Steven M. Bellovin
- Re: Patented RFC Code,
Frank Ellermann
- Re: Patented RFC Code,
Scott O. Bradner
- Re: Patented RFC Code,
Simon Josefsson
- Re: Patented RFC Code,
Scott O. Bradner
- Re: Patented RFC Code,
Harald Alvestrand
- Re: Patented RFC Code,
Frank Ellermann
- Case study: SHA2 (was: Re: Patented RFC Code),
Simon Josefsson
- Re: Case study: SHA2,
Harald Alvestrand
- RE: Case study: SHA2,
Lawrence Rosen
- Re: Case study: SHA2,
Frank Ellermann
- Re: Case study: SHA2,
Steven M. Bellovin
- RE: Case study: SHA2 (was: Re: Patented RFC Code),
Barr Hibbs
- Re: Case study: SHA2,
Simon Josefsson
- Message not available
- Re: Case study: SHA2,
Steven M. Bellovin
- Re: Case study: SHA2,
Frank Ellermann
- Re: IETF Trust FAQ,
Brian E Carpenter
Re: IETF Trust FAQ,
Simon Josefsson
Decisions from San Diego confirmed for next version of drafts,
Harald Alvestrand
#1400 Opinion poll - summary,
Harald Alvestrand
Mail converted by MHonArc
