search

ietf-wg-emailcore / emailcore

3 stars 0 forks source link

G.15 Rename/expand section 7.8 to "Resistance to Attacks and Local Operational Requirements" #48

Closed ietf-svn-bot closed 2 years ago

ietf-svn-bot commented 3 years ago

owner:alexey.melnikov@isode.com resolution_fixed type_defect | by alexey.melnikov@isode.com

John Klensin wrote:

Section 7.8 ("Resistance to Attacks"), which explicitly mentions large numbers of recipients, is not quite right for this. More generally, we've talked informally about flexibility for "operational necessity" for years (I even used that phrase in G.1) but it does not appear elsewhere in the document. I think it would be helpful to clarity to re-title 7.8 to "Resistance to Attacks and Local Operational Requirements" (or something similar) and probably to add a sentence or two there that would indicate that attack resistance is not the only issue that might justify local restrictions. If people agree, text welcome.

Issue migrated from trac:48 at 2022-01-31 12:37:46 +0000

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

John clarified this section in -03.

Suggested next action to check with the mailing list and close this ticket.

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com changed status from new to assigned

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com set owner to alexey.melnikov@isode.com

ietf-svn-bot commented 2 years ago

@alexey.melnikov@isode.com changed status from assigned to closed

ietf-svn-bot commented 2 years ago

@alexey.melnikov@isode.com set resolution to fixed