There is no such rule in the IETF, although perhaps patent discussions
need some moderation to avoid becoming ratholes. To quote some pieces
of text from RFC 3669 (which I recommend you read in full):
"It's all right, and sometimes beneficial, to discuss IPR claims
and gather information about possible prior art on the [working]
group list.
The results of such discussion can be considered when deciding
whether to develop a technology (but remember that neither the
IETF nor any working group takes a stand on such claims as a body,
and the group is not the best place to get legal advice)."
and
"Working group participants can evaluate IPR claims not only for
their possible validity, but also for the risk of misjudging that
validity."
Donald
=============================
Donald E. Eastlake 3rd
155 Beaver Street
Milford, MA 01757 USA
On Wed, Apr 14, 2010 at 8:47 AM, Trowbridge, Stephen J (Steve)
<steve.trowbridge@xxxxxxxxxxxxxxxxxx> wrote:
> Hi all,
> In IEEE we are admonished to never discuss the essentiality or validity of patent claims. I cannot believe this is considered an appropriate discussion in IETF.
> Regards,
> Steve
>
> -----Original Message-----
> From: pwe3-bounces@xxxxxxxx [mailto:pwe3-bounces@xxxxxxxx] On Behalf Of Yaakov Stein
> Sent: Wednesday, April 14, 2010 1:44 AM
> To: mmorrow@xxxxxxxxx; lmartini@xxxxxxxxx; tom.nadeau@xxxxxx; Aissaoui, Mustapha (Mustapha); david.i.allan@xxxxxxxxxxxx; Busschbach, Peter B (Peter)
> Cc: IETF@xxxxxxxxxxxxxx; Secretariat; pwe3@xxxxxxxx; adrian.farrel@xxxxxxxxxx; andrew.g.malis@xxxxxxxxxxx; stbryant@xxxxxxxxx
> Subject: Re: [PWE3] Posting of IPR Disclosure related to Cisco's Statement of IPR relating to draft-ietf-pwe3-oam-msg-map-12
>
>
> This disclosure (1311) quotes application US20080089227A1: Protecting multi-segment pseudowires which may impact draft-ietf-pwe3-redundancy, and perhaps ICCP, MS-PW architecture, and MS-PW setup.
> There is no apparent connection with oam-msg-map - in fact the claims stress that the triggers are failures of PSN elements (e.g. S-PEs) and are NOT from the ACs, making any connection untenable.
>
> A previous disclosure by the same company (863) refers to
> 20080285466 : Interworking between MPLS/IP and Ethernet OAM mechanisms which may impact mpls-eth-oam-iwk, but not oam-msg-map, unless one interprets the first claim and its dependents much more broadly than supported by the background and description.
>
> Can someone from the company claiming this IPR fix the information in these disclosures ?
> At very least that company is required to disclose IPR is holds with respect to the appropriate drafts (unless it is willing to risk forfeiting its rights with respect to these ...).
>
> However, with respect to oam-msg-map I would like to request that it consider removing inappropriate disclosures.
> Of course, if after consideration it believes that these disclosures ARE appropriate, I would love to hear the reasoning.
>
> Y(J)S
>
>
> -----Original Message-----
> From: IETF Secretariat [mailto:ietf-ipr@xxxxxxxx]
> Sent: Tuesday, April 13, 2010 18:46
> To: mmorrow@xxxxxxxxx; Yaakov Stein; lmartini@xxxxxxxxx; tom.nadeau@xxxxxx; Mustapha.aissaoui@xxxxxxxxxxxxxxxxxx; david.i.allan@xxxxxxxxxxxx; busschbach@xxxxxxxxxxxxxxxxxx
> Cc: stbryant@xxxxxxxxx; adrian.farrel@xxxxxxxxxx; pwe3@xxxxxxxx; andrew.g.malis@xxxxxxxxxxx; matthew.bocci@xxxxxxxxxxxxxxxxxx; ipr-announce@xxxxxxxx
> Subject: Posting of IPR Disclosure related to Cisco's Statement of IPR relating to draft-ietf-pwe3-oam-msg-map-12
>
> Dear Monique Morrow, Yaakov Stein, Luca Martini, Thomas Nadeau, Mustapha Aissaoui, David Allan, Peter Busschbach:
>
> An IPR disclosure that pertains to your Internet-Draft entitled "Pseudowire (PW) OAM Message Mapping" (draft-ietf-pwe3-oam-msg-map) was submitted to the IETF Secretariat on 2010-04-07 and has been posted on the "IETF Page of Intellectual Property Rights Disclosures" (https://datatracker.ietf.org/ipr/1311/). The title of the IPR disclosure is "Cisco's Statement of IPR relating to draft-ietf-pwe3-oam-msg-map-12."
>
> The IETF Secretariat
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@xxxxxxxx
> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> Ietf mailing list
> Ietf@xxxxxxxx
> https://www.ietf.org/mailman/listinfo/ietf
>
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf