RFC 3995, "Internet Printing Protocol (IPP): Event Notifications and Subscriptions", March 2005

Errata ID: 7516
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Tarak Parikh
Date Reported: 2023-05-15

Section 5.3 page 19 says:

   For Pull Delivery Methods, a client MUST supply "notify-recipient-
   uri" and MAY omit any of the rest of the attributes in column 1 of
   Table 1 in a Subscription Creation Request.  For Push Delivery
   Methods, a client MUST supply "notify-pull-method" and MAY omit any
   of the rest of the attributes in column 1 of Table 1 in a
   Subscription Creation Request.  A client MUST NOT supply both
   "notify-recipient-uri" and "notify-pull-method" attributes in the
   same Subscription Creation Request.

It should say:

   For Push Delivery Methods, a client MUST supply "notify-recipient-
   uri" and MAY omit any of the rest of the attributes in column 1 of
   Table 1 in a Subscription Creation Request.  For Pull Delivery
   Methods, a client MUST supply "notify-pull-method" and MAY omit any
   of the rest of the attributes in column 1 of Table 1 in a
   Subscription Creation Request.  A client MUST NOT supply both
   "notify-recipient-uri" and "notify-pull-method" attributes in the
   same Subscription Creation Request.

Notes:

notify-recipient-uri is used for Push notification method and notify-pull-method is used for pull notification method based on the paragraph based on the second paragraph in section 5.3 paragraph 2 "The "notify-recipient-uri" attribute is for use with Push Delivery
Methods. The "notify-pull-method" attribute is for use with Pull
Delivery Methods."
But in 4th Paragraph for client requirements there is a mistake. It mentions pull requires notification-recipient-uri instead of push requires and similarly verbage is wrong for push as well which indicates clients must use notify-pull-method

Report New Errata