Opened 8 years ago

Closed 8 years ago

#186 closed defect (fixed)

Routing error

Reported by: jouni.nospam@… Owned by: jouni.nospam@…
Priority: major Milestone:
Component: dynamic-discovery Version:
Severity: - Keywords:
Cc:

Description

As a pert of the document shepherd proto write-up I read the I-D.

In Section 1.3. it is claimed:

o a partially correct routing error detection (not considered for

Diameter)

What is considered missing in Diameter here? Diameter does detect routing loops without it being part of the dynamic discovery. The discovery mechanism in RFC6733 and 6408 does not protect against a loop in DNS query though (that is implementation specific).

Change History (1)

comment:1 Changed 8 years ago by stefan.winter@…

  • Resolution set to fixed
  • Status changed from new to closed

The error detection is specific to DNS; since RADIUS does not have the equivalent of a Route-Record AVP, this is the only place to put a loop detection.

It's quite correct that Diameter has its own mechanism, and can thus ignore how the loop was constructed (i.e. leave DNS lookup loops as implementation specific).

I have removed the parenthesis and added "during DNS lookups" to qualify the sentence.

This should close the ticket.

Note: See TracTickets for help on using tickets.