A few notes, Amanda:

CIRA Fury-rgp-1.0 EPP Extension: The registration template is fine. The 
extension is using an IETF namespace (urn:ietf:params:xml:ns:fury-rgp-1.0) for 
the extension's XML namespace and schema. They shouldn't do that because this 
isn't an IETF specification. They should use their own private namespace.

CIRA Fury-2.1 EPP Extension: The registration template is fine. The extension 
is using an IETF namespace (urn:ietf:params:xml:ns:fury-2.1) for the 
extension's XML namespace and schema. They shouldn't do that because this isn't 
an IETF specification. They should use their own private namespace.

Scott

> -----Original Message-----
> From: Amanda Baber via RT <[email protected]>
> Sent: Tuesday, September 30, 2025 8:16 PM
> Cc: Hollenbeck, Scott <[email protected]>
> Subject: [EXTERNAL] [IANA #1431007] INSERT: EPP Extensions — CIRA fury-rgp-
> 1.0 and fury-2.1
> 
> Caution: This email originated from outside the organization. Do not click 
> links
> or open attachments unless you recognize the sender and know the content is
> safe.
> 
> Hi Scott,
> 
> Would it be possible to review these two EPP Extension proposals for us by
> October 14th?
> 
> thanks,
> Amanda
> 
> =====
> 
> Hello IANA,
> 
> Per RFC 7451, please find below two registration forms to INSERT new entries
> into the “Extensions for the Extensible Provisioning Protocol (EPP)” 
> registry. The
> specifications are publicly available at the URLs shown in the “Reference” 
> fields.
> 
> If any additional information is required during review, we’re happy to 
> provide
> it.
> 
> Thank you,
> Don Slaunwhite
> 
> Form 1: CIRA fury-rgp-1.0
> 
> 
> -----BEGIN FORM-----
> 
> Name of Extension:
> 
> "CIRA Fury RGP Information for the Extensible Provisioning Protocol (EPP) "
> 
> Document Status:
> 
> Informational
> 
> Reference:
> 
> https://secure-
> web.cisco.com/1WmubtFklMSV8lDsdaJf4YQmbMElz795tYO8oZKGQMdGHbXuV
> 3s_9G34RYDi9D8erqwPsbITEa7qZRZ6Tz3hP-
> xgqvaGagEu_ucyWyIDw8NMlEUv_6pwSQtES4MfQo_o6RmwffbjC0sDL-
> MaKNA39mVxb065sGidsf2wJeFOV7i31ZFiJXqlyHytIiviLnGbGiBiqO3ieDOmk50aQ
> UN2J8NG2RIDwZUOqyGml5djzU5S_HZSjPStbs5vzNzrLjJliFJ6U_MguGuQInLXXS56
> oZHB0cHkmymhBVIlOV-
> YU9t4/https%3A%2F%2Fwww.cira.ca%2Fen%2Fresources%2Fdocuments%2Fregi
> stry%2Fcira-fury-rgp-1-epp-extension%2F
> 
> Registrant Name and Email Address:
> 
> Canadian Internet Registration Authority (CIRA), [email protected]
> 
> TLDs: Any
> 
> IPR Disclosure: None
> 
> Status: Active
> 
> Notes: "Provides extended information about the Redemption Grace Period
> (RGP) status for a domain."
> 
> -----END FORM-----
> 
> 
> Form 2: CIRA fury-2.1
> 
> 
> -----BEGIN FORM-----
> 
> Name of Extension:
> 
> "CIRA Fury 2.1 Extension for the Extensible Provisioning Protocol (EPP) "
> 
> Document Status:
> 
> Informational
> 
> Reference:
> 
> https://secure-web.cisco.com/1-
> bh6fauKa77Z2JaYWJnP2lX5uSk3dWsjuBzcLbDiqwEPM9KRtIzbdJYP63GCAsb6XKd
> MWsblqXxWXfA0E8hCoRvRPVYHhTQ7MUfg2u_0yZ9eWJf7YctbAFT4PAqXgVOInI
> Q_YDdcU_7XJvNMU3yXlAoiEA6ID5v7lWmJtnkdSRtvUrfioVaPsWmj2DGl8HoTlJ2l
> diwnknPoP5AyEaqcDl0GOuxts1Lr4vEPQXFuEBlZ8li4w-
> jbqkZk_toJQZRVgV_q8Fll2MKPbHZuhHl1LLi1uS2BiyyV77NGmXJZIBI/https%3A%2
> F%2Fwww.cira.ca%2Fen%2Fresources%2Fdocuments%2Fregistry%2Fcira-fury-
> 21-epp-extension%2F
> 
> Registrant Name and Email Address:
> 
> Canadian Internet Registration Authority (CIRA), [email protected]
> 
> TLDs: Any
> 
> IPR Disclosure: None
> 
> Status: Active
> 
> Notes: " Provides registry-defined properties across EPP objects, extended 
> error
> handling via secondary codes, and administrative bundles that enforce
> registrant consistency."
> 
> 
> -----END FORM-----
> 
> 
> CLASSIFICATION:CONFIDENTIAL
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to