Re: [Roll] IETF 109 open Questions on P-DAO

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Fri, 27 November 2020 07:43 UTC

IronPort-PHdr: 9a23:85kHqhDWFhbOkTXY4qOWUyQJPHJ1sqjoPgMT9pssgq5PdaLm5Zn5IUjD/qw01g3IUJnVrfVehLmev6PhXDkG5pCM+DAHfYdXXhAIwcMRg0Q7AcGDBEG6SZyibyEzEMlYElMw+Xa9PBtUFdrwIVrIrS764TsbAB6qMw1zK6z8EZLTiMLi0ee09tXTbgxEiSD7b6l1KUC9rB7asY8dho4xJw==3D
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: IETF 109 open Questions on P-DAO
Thread-Index: AdbCY32NelMcR5MvThCvhSSTyZHQKgCLIpZA
Date: Fri, 27 Nov 2020 07:43:18 +0000
Deferred-Delivery: Fri, 27 Nov 2020 07:43:14 +0000
Message-ID: <CO1PR11MB48818AF6B81AED230CF30B92D8F80@CO1PR11MB4881.namprd11.prod.outlook.com>
References: <CO1PR11MB4881B348B4A224DBAEE5BA74D8FB0@CO1PR11MB4881.namprd11.prod.outlook.com>
In-Reply-To: <CO1PR11MB4881B348B4A224DBAEE5BA74D8FB0@CO1PR11MB4881.namprd11.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_CO1PR11MB48818AF6B81AED230CF30B92D8F80CO1PR11MB4881namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c74a865e-b0d6-4349-6cdd-08d892a82ec9
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Nov 2020 07:43:50.8196 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: FfZuenYZr+i+VWtT5e1EC1fQZQWs7Fo18N4ZgrFj1+2vGLTl3z2oCj+hLSn4k1Q+33Le5pk1kEvuvXeSSqZImQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR11MB5091
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/9x2lzH_IRiRCHpvz7PDL31yLtpY>
Subject: Re: [Roll] IETF 109 open Questions on P-DAO
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Nov 2020 07:43:57 -0000

Dear all:

Updating the list:


  1.  Lifetime Unit: could we use a different unit for P-DAO?
  2.  How to differentiate a P-DAO from a normal DAO in a local instance; new flag?
  3.  Make P-DAO bidirectional?
  4.  Who sends the PDR? Does it have to be the ingress? If it was egress it could propose a TrackId from its namespace. Else could the ingress be the root?
  5.  Maintaining the sibling state. Should we have text on using RFC 8505 there?
  6.  Whether ingress and egress are listed in NPO? Today they are both, ingress to indicate the packet source in case of encapsulation and for SRH-6LoRH compression reference and egress to build the full SRH-6LoRH. Note that the ingress must consume the first entry and use it as source.
  7.  Track in Track vs. SR Header reload models, see slides
  8.  Error flows, which ICMP errors and to which root? The draft should present the flows.
  9.  how can the Main Root find an available TrackID?

Keep safe;

Pascal



From: Pascal Thubert (pthubert)
Sent: mardi 24 novembre 2020 14:22
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: IETF 109 open Questions on P-DAO

Dear all

The slides for the P-DAO discussion at IETF 109 are available here:

https://datatracker.ietf.org/doc/slides-109-roll-dao-projection/

There are a number of open questions that we starting discussing, and would need to progress on the list.
Some of them were expressed on the list, e.g., from Huimin She. I'd like to progress on them all with individual threads.
The questions are:


  1.  Lifetime Unit: could we use a different unit for P-DAO?
  2.  How to differentiate a P-DAO from a normal DAO in a local instance; new flag?
  3.  Make P-DAO bidirectional?
  4.  Who sends the PDR? Does it have to be the ingress? If it was egress it could propose a TrackId from its namespace. Else could the ingress be the root?
  5.  Maintaining the sibling state. Should we have text on using RFC 8505 there?
  6.  Whether ingress and egress are listed in NPO? Today they are both, ingress to indicate the packet source in case of encapsulation and for SRH-6LoRH compression reference and egress to build the full SRH-6LoRH. Note that the ingress must consume the first entry and use it as source.
  7.  Track in Track vs. SR Header reload models, see slides

Let me open threads to follow up.

Keep safe

Pascal

[Roll] IETF 109 open Questions on P-DAO Pascal Thubert (pthubert)
Re: [Roll] IETF 109 open Questions on P-DAO Huimin She (hushe)
Re: [Roll] IETF 109 open Questions on P-DAO Pascal Thubert (pthubert)
Re: [Roll] IETF 109 open Questions on P-DAO Pascal Thubert (pthubert)