Re: cops-pr and sppi to historic

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============5753441820871542071==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="UFx4c2gFIsEjEaGR1vcvJ1tJvkUXVp5OS"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--UFx4c2gFIsEjEaGR1vcvJ1tJvkUXVp5OS
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 11/24/15 12:37 AM, Romascanu, Dan (Dan) wrote:
> Time has come (again).
>=20
> I support this. During my tenure as AD we discussed this issue once
> or twice and stopped short because of concerns about possible
> implementations and deployment. The public process described in [2]
> gives the opportunity for anybody who is aware of such
> implementations and would be in any way impacted negatively by the
> decision to go to Historic to step out and express his/her
> opposition.

+1

thanks
joel

> Regards,
>=20
> Dan
>=20
>=20
>> -----Original Message----- From: OPS-AREA
>> [mailto:[email protected]] On Behalf Of Benoit Claise Sent:
>> Monday, November 23, 2015 11:33 PM To: [email protected] Subject:
>> [OPS-AREA] cops-pr and sppi to historic
>>=20
>> Dear all,
>>=20
>> J=C3=BCrgen has posted draft-schoenw-opsawg-copspr-historic-03 [1] and=

>> we like to request the process described in [2] item 2.
>>=20
>> Would anybody oppose this? If not answer within a week, I'll start
>> the process. As far as I know, there are no more active
>> COPS-related email lists at the IETF. Hence this mailing list.
>>=20
>> [1] https://urldefense.proofpoint.com/v2/url?u=3Dhttps-=20
>> 3A__datatracker.ietf.org_doc_draft-2Dschoenw-2Dopsawg-2Dcopspr-=20
>> 2Dhistoric_&d=3DBQIGaQ&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJ =

>> fQzvlsiLQfucBXRucPvdrphpBsFA&m=3DdeqSLi8_0WMpFMJcraxo7O3DBlFZijRee=20
>> Msoy5VBduM&s=3D3OIKUwhG54BYnsIsvujEUJEjRuzphgz0QfrDdc2w2yQ&e=3D [2]
>> https://urldefense.proofpoint.com/v2/url?u=3Dhttp-=20
>> 3A__www.ietf.org_iesg_statement_designating-2Drfcs-2Das-=20
>> 2Dhistoric.html&d=3DBQIGaQ&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31Oc =

>> NXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3DdeqSLi8_0WMpFMJcraxo7O3DBlFZ=20
>> ijReeMsoy5VBduM&s=3DormSeZS9C7LxrLg9RvmdaGnskLPgmMzezZhiLYDmo4I &e=3D
>>=20
>> Regards, Benoit
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________ OPS-AREA mailing
>> list [email protected]=20
>> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-=20
>> 3A__www.ietf.org_mailman_listinfo_ops-=20
>> 2Darea&d=3DBQIGaQ&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNXCJfQz=20
>> vlsiLQfucBXRucPvdrphpBsFA&m=3DdeqSLi8_0WMpFMJcraxo7O3DBlFZijReeMs=20
>> oy5VBduM&s=3DiQotz0CfN9X-HwSaLwrb5PCN4UIOzc9I5kWduqkx7M0&e=3D
> _______________________________________________ OPS-AREA mailing
> list [email protected]=20
> https://www.ietf.org/mailman/listinfo/ops-area
>=20



--UFx4c2gFIsEjEaGR1vcvJ1tJvkUXVp5OS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlZU3/EACgkQ8AA1q7Z/VrLAWgCfcjkFyrUBEtrnOejSL5rIaqP9
CwQAnAiCIpQwaAIBHi3wPHW85J5azx7N
=2rOJ
-----END PGP SIGNATURE-----

--UFx4c2gFIsEjEaGR1vcvJ1tJvkUXVp5OS--


--===============5753441820871542071==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
OPS-AREA mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ops-area

--===============5753441820871542071==--