public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dave@treblig.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] man/man5/gai.conf: Labels have a label not a precedence
Date: Sun, 4 Jan 2026 22:52:59 +0000	[thread overview]
Message-ID: <aVrvS17o3Pq7e-Tq@gallifrey> (raw)
In-Reply-To: <aVroLT4toQaQD2nn@devuan>

* Alejandro Colomar (alx@kernel.org) wrote:
> Hi David,

Hi Alex,

> On Sun, Jan 04, 2026 at 10:04:38PM +0000, dg@treblig.org wrote:
> > From: "Dr. David Alan Gilbert" <dave@treblig.org>
> > 
> > The numeric value on a label entry is a label which is separate
> > from the precedences.  Labels are compared with other labels, not
> > precedences.
> 
> Is there any source to verify this?

The two I checked are:
  https://datatracker.ietf.org/doc/html/rfc3484#section-2.1
    is the RFC itself, and it talks about the Precedence and labels
as separate values.  Note how it's talking in terms of:

   If Precedence(A) > Precedence(B), we say that...
and
   The algorithms prefer to use a source address S with a destination
   address D if Label(S) = Label(D).

So it's label compared to label and precedence compared to precedence.

The corresponding bits of glibc are:
https://sourceware.org/git/?p=glibc.git;a=blob;f=nss/getaddrinfo.c;h=c0f496f96c752220e68bf0257d9ff1ffc624ebe6;hb=HEAD#l1525

where the label values are compared in Rule 5, and the precedence values
are compared in Rule 6.

Dave

> 
> Cheers,
> Alex
> 
> > 
> > Rename the field.
> > 
> > Signed-off-by: Dr. David Alan Gilbert <dave@treblig.org>
> > ---
> >  man/man5/gai.conf.5 | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/man/man5/gai.conf.5 b/man/man5/gai.conf.5
> > index 4aff0b0b9..ef330995d 100644
> > --- a/man/man5/gai.conf.5
> > +++ b/man/man5/gai.conf.5
> > @@ -26,7 +26,7 @@ .SH DESCRIPTION
> >  .P
> >  The keywords currently recognized are:
> >  .TP
> > -.BI label\~ netmask\~precedence
> > +.BI label\~ netmask\~label
> >  The value is added to the label table used in the RFC\ 3484 sorting.
> >  If any
> >  .B label
> > @@ -35,7 +35,7 @@ .SH DESCRIPTION
> >  All the label definitions
> >  of the default table which are to be maintained have to be duplicated.
> >  Following the keyword,
> > -the line has to contain a network mask and a precedence value.
> > +the line has to contain a network mask and a label value.
> >  .TP
> >  .BI precedence\~ netmask\~precedence
> >  This keyword is similar to
> > -- 
> > 2.52.0
> > 
> 
> -- 
> <https://www.alejandro-colomar.es>


-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\        dave @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  reply	other threads:[~2026-01-04 22:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-04 22:04 [PATCH] man/man5/gai.conf: Labels have a label not a precedence dg
2026-01-04 22:23 ` Alejandro Colomar
2026-01-04 22:52   ` Dr. David Alan Gilbert [this message]
2026-01-14 14:26     ` Dr. David Alan Gilbert
2026-01-14 20:17       ` Alejandro Colomar
2026-01-14 21:16         ` Dr. David Alan Gilbert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aVrvS17o3Pq7e-Tq@gallifrey \
    --to=dave@treblig.org \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox