[Openid-specs-authzen] [openid/authzen] incorporated subject identifiers from RFC9493 (PR #57)

Atul Tulshibagwale atul at sgnl.ai
Wed Dec 13 00:01:46 UTC 2023


Hi Roland,
The PR refers to RFC4001, which defines the string representation of IP
addresses. We expect this string value in the IP Address field. Does
that make sense?

Thanks,
Atul


On Tue, Dec 12, 2023 at 4:00 PM Atul Tulshibagwale <atultulshi at gmail.com>
wrote:

>
>
> ---------- Forwarded message ---------
> From: tr33 <notifications at github.com>
> Date: Tue, Dec 12, 2023 at 11:26 AM
> Subject: Re: [openid/authzen] incorporated subject identifiers from
> RFC9493 (PR #57)
> To: openid/authzen <authzen at noreply.github.com>
> Cc: Atul Tulshibagwale <atultulshi at gmail.com>, Author <
> author at noreply.github.com>
>
>
> question to definition of
>
> "format": "ip_address",
>
> the examples only contain IPv4 adresses. But IPv4 is overaged and new
> systems must be IPv6 compatible.
> however, both address formats will remain in the wild for sure a long time.
>
> Question: should the *ip address be typed* in order to distinguish
> between multiple versions an formats?
> like to distinguish between address netmask (a.b.c.d/24) and IPv6?
>
> also, IPv6 address can be formatted ambiguously (see Issue #46
> <https://github.com/openid/authzen/issues/46> )
>
>> Reply to this email directly, view it on GitHub
> <https://github.com/openid/authzen/pull/57#issuecomment-1852672058>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AB55UG4OTT4PTJLXKF3A7OLYJCVWVAVCNFSM6AAAAABAQR2NESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJSGY3TEMBVHA>
> .
> You are receiving this because you authored the thread.Message ID:
> <openid/authzen/pull/57/c1852672058 at github.com>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-authzen/attachments/20231212/d69abd02/attachment.html>


More information about the Openid-specs-authzen mailing list